-
Notifications
You must be signed in to change notification settings - Fork 204
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
Rotate SQL User credentials #856
Conversation
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
…-service-operator into sqluser-rollcreds
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good to me and local test run worked great
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM #3
Closes #537
What this PR does / why we need it:
Currently there is a way to roll admin credentials to the SQL server, but not SQL Database user credentials. This extends SQL Action to add that functionality.
When checking if the user exists or not, the code was using the kube namespaced name exclusively, thus it would always come up as a negative if the secret client was Key Vault. Refactored logic around with
dbUserCustomNamespace
, put the check for the sql user secret key value into one function.Special notes for your reviewer:
To test:
rollusercreds
. Specify SQL User from above. Observe in Key Vault that credentials have updated.How does this PR make you feel:
If applicable: