Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow externalisation of secrets #38

Open
sheu opened this issue Mar 18, 2021 · 0 comments
Open

Allow externalisation of secrets #38

sheu opened this issue Mar 18, 2021 · 0 comments

Comments

@sheu
Copy link

sheu commented Mar 18, 2021

When running the replicator executable, the user is required to provide secrets in the consumer and producer properties file. So far I have identified 3 values which are:

  1. password in sasl.jaas.config field
  2. ssl.keystore.password
  3. ssl.truststore.password

It will be great if these value can be read as environment variables which are then merged into their respective files. An example will be to have the following environment variables:

  1. CONSUMER_SASL_JAAS_CONFIG
  2. PRODUCER_SASL_JAAS_CONFIG
  3. CONSUMER_SSL_KEYSTORE_PASSWORD
  4. CONSUMER_SSL_TRUSTSTORE_PASSWORD
  5. PRODUCER_SSL_TRUSTSTORE_PASSWORD
  6. PRODUCER_SSL_KEYSTORE_PASSWORD

The motivation behind this is that the files when deploying replicator in kubernetes environment keeping the configuration as code, the secrets will not be leaked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant