💡 [Feature] - allow supplying a key/truststore directly rather than via a path #173
Description
Description
The connector currently provides the following configuration items for supplying a key/truststore:
- mq.ssl.keystore.location
- mq.ssl.truststore.location
Both of these expect the value to be a path. This forces the user to use a volume mount to provide the key/truststore files at a known location within the Kafka Connect pod file system.
It would be good to provide a peer configuration item that allows the key/truststore file content to be supplied directly as a String. This avoids the need to configure a volume mount and allows the use of the Strimzi ConfigProvider classes as described @ https://strimzi.io/docs/operators/latest/deploying#assembly-loading-config-with-providers-str
Suggested Solution
It would be good to provide peer configuration items that allows the key/truststore file content to be supplied directly as a String.
This avoids the need to configure a volume mount and allows the use of the Strimzi ConfigProvider classes as described @ https://strimzi.io/docs/operators/latest/deploying#assembly-loading-config-with-providers-str
Suggested new configuration items could be:
- mq.ssl.keystore.content
- mq.ssl.truststore.content
It should be possible to read the String content as an InputStream directly into the appropriate Java classes. However, it would be necessary to prevent both content and location values from being supplied as it should be obvious to the user that use of content vs. location is an either/or decision.
Alternatives
No response
Additional Context
No response