oscerd opened a new issue, #2954:
URL: https://github.com/apache/camel-kamelets/issues/2954
The OpenSearch Kamelets and their Elasticsearch counterparts declare the
same property at the same position with opposite defaults:
| Kamelet | `enableSSL` default |
|---|---|
| `elasticsearch-index-sink` | `true` |
| `elasticsearch-search-source` | `true` |
| `opensearch-index-sink` | **`false`** |
| `opensearch-search-source` | **`false`** |
The property title and description are identical between the pairs
("Specifies to connect by using SSL." / "Do we want to connect using SSL?"), so
the divergence looks unintentional rather than deliberate.
Proposal: align the OpenSearch pair with the Elasticsearch pair (`default:
true`) and add an upgrade-guide note, since it changes behaviour for existing
deployments pointing at plain-HTTP clusters.
Affected:
- `kamelets/opensearch-index-sink.kamelet.yaml`
- `kamelets/opensearch-search-source.kamelet.yaml`
Related: #2791 (opensearch kamelets: Advanced TLS/mTLS configuration
options).
_Claude Code on behalf of Andrea Cosentino_
--
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]
