fix: app-proxy does not monitor and re-create the argocd-token if it was already created before the Pod started #782
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.
Bumps
app-proxy
to version788a8d5
(https://github.com/codefresh-io/argo-platform/pull/6723)app-proxy env vars should only contain ARGO_CD_USERNAME and ARGO_CD_PASSWORD or ARGO_CD_TOKEN
cherry-pick most of the changes from #768 - updated template to include the correct env vars that app-proxy expects. did not make any breaking changes in values, so argo-cd auth values are still located at
global.external-argo-cd.auth