-
Notifications
You must be signed in to change notification settings - Fork 188
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
Redis Secret Password Key #434
Redis Secret Password Key #434
Conversation
- Added `redisSecretPasswordKey` value Added a new `redisSecretPasswordKey` value that allows users to override the default `password` key used when specifying an existing `Secret` for Redis. This makes for a more seamless integration with popular third-party Redis Helm charts. Signed-off-by: John Lahr <john@johnlahr.me>
4b90e6d
to
b538425
Compare
Hi @JohnLahr, thank you for the contribution! Would you mind adding a couple of unit test cases to test this? |
Co-authored-by: Gabriel Martinez <19713226+GMartinez-Sisti@users.noreply.github.com> Signed-off-by: John <john@johnlahr.me>
Signed-off-by: John Lahr <john@johnlahr.me>
@GMartinez-Sisti Added unit tests. Not as familiar with writing tests for charts, but I think I had enough context to work with. Let me know if those aren't sufficient! |
Thanks @JohnLahr! They look great. Now there’s just one small update requirement for the docs. Please check the job that failed. |
Signed-off-by: John Lahr <john@johnlahr.me>
77b80fc
to
fa9d1d1
Compare
Apologies. That should be fixed now 👍 |
Signed-off-by: John Lahr <john@johnlahr.me>
No need for apologies! Thank you again for the contribution 😁 |
what
redisSecretPasswordKey
valuepassword
value as default for backward-compatibilitywhy
This allows users to override the default
password
key used when specifying an existingSecret
for Redis. This makes for a more seamless integration with popular third-party Redis Helm charts.For example, the Bitnami Redis chart creates a secret called
<release>-redis
with a key calledredis-password
whose value is the password generated for that Redis distribution. Allowing users to specify an arbitrary key name means they can seamlessly integrate that Redis chart with this Atlantis chart and use the same secret.tests
I have tested this successfully in an Amazon EKS cluster.
references
N/A