davsclaus commented on issue #3170: URL: https://github.com/apache/camel-kamelets/issues/3170#issuecomment-6974777746
## Second wave With the first table done, these are the next gaps to fix. Each is a gap that makes a Kamelet unusable in a common production setup, or makes it lose data. As before, there is one PR per family, each tested against a local stand-in of the service. | Kamelet | Gap | Why | |---|---|---| | `cassandra-sink` | `datacenter`, TLS | The local datacenter is fixed to `datacenter1`, so a cluster whose datacenter has another name cannot be used | | `azure-eventhubs-source` | `consumerGroupName`, `eventPosition` | It reads only with the `$Default` consumer group, so two integrations cannot read the same hub on their own | | `aws-sqs-source` | `messageAttributeNames`, `attributeNames` | The message attributes are always empty | | `mqtt-*`, `mqtt5-*` | `qos`, `retained`, TLS | Only QoS 0, so messages can be lost; no TLS with a private CA | | `ftp-sink`, `ftps-sink`, `sftp-sink` | `tempFileName` or `tempPrefix`, `doneFileName` | A reader can pick up a half-written file | | `ssh-*`, `scp-sink` | Login with a key | Many servers turn off password login | | `http-sink`, `http-source` | A trust store, `okStatusCodeRange`, a static bearer token | Services behind a private CA, and APIs that answer a normal case with a 4xx code | | `mongodb-*` | A connection string (`mongodb+srv`, Atlas), `authSource` | MongoDB Atlas cannot be used | | `exec-sink` | Arguments | No argument can be passed to the program | The first four come first. The `rows` option of `solr-source` and TLS for `jms-ibm-mq-*` (`sslCipherSuite`) already exist, so they are not listed. Later: - **The proxy options of all the AWS Kamelets:** a mechanical change to about 30 Kamelets, in a PR of its own. - **Login with a key pair for Snowflake:** first check whether Snowflake still allows a service user to log in with only a password. _Claude Code on behalf of Claus Ibsen_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
