feat: add ability to define extra postgres users #19
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcellmueller
temporarily deployed
to
development
GitHub Actions
Inactive
marcellmueller
temporarily deployed
to
production
GitHub Actions
Inactive
marcellmueller
force-pushed
the
feat/allow-extra-postgres-users
branch
from
54fd7c6 to
d608059
Compare
marcellmueller
temporarily deployed
to
development
GitHub Actions
Inactive
marcellmueller
temporarily deployed
to
production
GitHub Actions
Inactive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implements #18
I decided to keep the required original users defined in
postgresCluster.yamlso that we could keep the template variables and keep it simpler for users if they changed the database name.This will still allow the creation of additional users if
postgres.extraUsers.enabledis set to true.