Update creation of default roles and users in Community#138
Draft
ben-sutherland-ot wants to merge 7 commits intomainfrom
Draft
Update creation of default roles and users in Community#138ben-sutherland-ot wants to merge 7 commits intomainfrom
ben-sutherland-ot wants to merge 7 commits intomainfrom
Conversation
…ername - which would cause headaches with silently skipping from users defined in parent charts
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Both IDOL Find and IDOL Data Admin require certain specific roles to be available in Community. Previously we have used post start scripts to achieve this, but this can become messy when consuming Find/Data Admin as a subchart. In 26.3 we will have the ability to create users with specified credentials and roles upon start up from the configuration file, so prepare the Community chart to allow for this. Try to preserve backwards compatibility for older images where possible, and in cases where the values must be updated (Data Admin), then describe in said values what needs to change for older Community versions.
Leaving as a draft until we release 26.3 to avoid confusion with values and config files that don't do anything yet.