Lookup existing argo workflows postgres secret before generating anew #92
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
garryod
added
bug
garryod
force-pushed
the
avoid-recreating-argo-workflows-postgres-secret
branch
from
0f1acf1
to
f18c656
Compare
Co-authored-by: Benedikt Daurer <benedikt.daurer@diamond.ac.uk>
garryod
force-pushed
the
avoid-recreating-argo-workflows-postgres-secret
branch
from
f18c656
to
a77571e
Compare
daurer
approved these changes
Jul 25, 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.
Checks for the existence of a argo workflows postgres passwords secret instead of relying on the helm
.Release.isUpgradevalue to determine whether a new password should be generated. This should resolve the issue in which the Argo Workflows server gets a new password but the one in the database remains