fix: use the correct default configmap name in deployment #210
Conversation
This file contains 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
|
@BitForger, please add a helm chart bump and edit the artifacthub.io/changes section. |
pierluigilenoci
approved these changes
May 31, 2024
|
@BitForger Thank you. |
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.
If you wish to use the default config map and only supply emails in
authenticatedEmailsFile.restricted_usersoption, the chart doesn't include the proper reference to the default config map name. See below:manifests/helm/oauth2-proxy/templates/configmap-authenticated-emails-file.yaml
Line 13 in 6116131