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 username to be specified in persistence secrets #601

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

dcaputo-harmoni
Copy link

What was changed

This commit allows the username to be specified alongside the password in persistence credentials secrets.

Why?

Many dynamic database creds generation / rotation systems (such as Hashicorp Vault) generate both the username and password dynamically, which is more secure than just generating / rotating passwords. The functionality has been updated to allow either or both of these to be optionally set via a secret with any or both of username and password keys.

@dcaputo-harmoni dcaputo-harmoni requested a review from a team as a code owner October 26, 2024 13:55
@robholland
Copy link
Contributor

This is a backwards incompatible change. While we can consider optionally storing the username in a secret, I don't want to force that.

@robholland robholland added the needs revision Team has requested some changes label Nov 5, 2024
@dcaputo-harmoni
Copy link
Author

@robholland There are two commits that are part of this PR, in the second one I added username to server-secret.yaml (in the same manner as password) - does that not make it backwards compatible such that if password is specified directly it will be included in the secret? If not, let me know what you're looking for here and I'd be happy to revise it.

@4FunAndProfit
Copy link

I can confirm that it would be great to have this! It blocks me too so it must block quite a few :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs revision Team has requested some changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants