oscerd opened a new issue, #2828: URL: https://github.com/apache/camel-kamelets/issues/2828
## Description The `jms-amqp-10` kamelets currently maintain separate SSL variants (`jms-amqp-10-ssl-source.kamelet.yaml` and `jms-amqp-10-ssl-sink.kamelet.yaml`) alongside their non-SSL counterparts (`jms-amqp-10-source.kamelet.yaml` and `jms-amqp-10-sink.kamelet.yaml`). This is inconsistent with how all other kamelets in the catalog handle SSL/TLS — Kafka, MongoDB, Elasticsearch, OpenSearch, and other kamelets include SSL/TLS configuration as built-in optional parameters within a single kamelet definition rather than maintaining separate files. ## Affected Files - `kamelets/jms-amqp-10-source.kamelet.yaml` - `kamelets/jms-amqp-10-ssl-source.kamelet.yaml` - `kamelets/jms-amqp-10-sink.kamelet.yaml` - `kamelets/jms-amqp-10-ssl-sink.kamelet.yaml` ## Expected Behavior Consolidate each pair into a single kamelet with optional SSL parameters (e.g., `sslEnabled`, `trustStoreLocation`, `trustStorePassword`, `keyStoreLocation`, `keyStorePassword`), following the same pattern used by Kafka and other kamelets. The separate SSL variant files should be removed. ## Additional Context - No other kamelets in the catalog follow the separate-SSL-variant pattern — only JMS AMQP 10 - Other JMS kamelets (Apache Artemis, IBM MQ) do not have SSL variants at all - Target release: **4.21.0** -- 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]
