External Secrets Updates for Sower #169
Merged
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
…environment variables instead of mounting the json secret file. I had to make changes to the pelican-export image in order to do this, so I am also changing the default pelican-export image as well.
EliseCastle23
changed the title
jawadqur
approved these changes
Apr 19, 2024
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.
Bug Fixes
Adding pelicanservice-g3auto to external secrets and using peregrine-dbcreds environment variables instead of mounting the json secret file. I had to make changes to the pelican-export image in order to do this, so I am also changing the default pelican-export image as well.
Breaking Changes
If a local peregrine-creds secret was created to get the PFB export to work- it will no longer work if you are using the default sower values.