-
Notifications
You must be signed in to change notification settings - Fork 17
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
Remove plaintext secret option #73
Conversation
get up to date with master
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kgcarr The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@kgcarr Please update the API as well |
} | ||
|
||
user = createRandomAlphaNumeric(8) | ||
pass = createRandomAlphaNumeric(13) |
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.
how to make this consist during the mongodb operator restart?
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.
@chenzhiwei the deployment supports changing the admin password on restarts, so it's ok for the admin secret to change
/lgtm |
This is the first part to address issue #67
We will not allow plaintext in the CR for username and password...so we will only allow random string admin and password
We will have to target adding a user supplied secret in Q2