[charts/argo-cd] add support of custom environment variables #181
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
|
|
Signed-off-by: Léo Depriester <leo.depriester@camptocamp.com>
cryptobioz
force-pushed
the
feature/argocd/extra-env-var
branch
from
24978ea to
02c8493
Compare
seanson
approved these changes
Dec 5, 2019
charts/argo-cd/templates/argocd-application-controller/deployment.yaml
Outdated
Show resolved
Hide resolved
seanson
approved these changes
Dec 5, 2019
|
Tested locally, all good! Thanks for the PR @cryptobioz! |
|
Thanks @seanson! |
5 tasks
nouseforaname
pushed a commit
to nouseforaname/argo-helm
that referenced
this pull request
Jan 29, 2020
…j#181) Signed-off-by: Léo Depriester <leo.depriester@camptocamp.com> * Fix controller env path * Updating chart bump to patch as this is a backwards compatible change
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.
Checklist:
Chart.yamlfollowing Semantic Versioning.Changes are automatically published when merged to
master. They are not published on branches.