You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I like my overrides checked in to git. While .argocd-source.yml is nice, in practice, I find that I want to use the overriden images for other purposes too, e.g., setting up a local Minikube environment. It sucks that I can't get updated images when using the same base with local kustomize. The end result is that my local environment has to be manually and painstakingly updated while my dev environment is always up to date.
Describe the solution you'd like
Update kustomization.yml instead. Can be done easily with kustomize edit set image. I think it would just look like one more write back method, and be implemented as such.
Describe alternatives you've considered
Other options I considered:
Run a script in my CI that parses the file and runs the right kustomize edit set image commands. That's yet another commit, and increases the odds of causing some kind of weird CI+CD feedback loop.
A kustomize plugin - painful for end users to consume.
I'll probably do this myself in the next few days and submit a PR, but thought I should put this in to see if anyone else has thoughts on it.
The text was updated successfully, but these errors were encountered:
* feat: allow write-back to actual kustomization files #199
* fix: was not handling default path correctly
default is the source path
* fix: sort imports
Is your feature request related to a problem? Please describe.
I like my overrides checked in to git. While
.argocd-source.yml
is nice, in practice, I find that I want to use the overriden images for other purposes too, e.g., setting up a local Minikube environment. It sucks that I can't get updated images when using the same base with local kustomize. The end result is that my local environment has to be manually and painstakingly updated while my dev environment is always up to date.Describe the solution you'd like
Update
kustomization.yml
instead. Can be done easily withkustomize edit set image
. I think it would just look like one more write back method, and be implemented as such.Describe alternatives you've considered
Other options I considered:
kustomize edit set image
commands. That's yet another commit, and increases the odds of causing some kind of weird CI+CD feedback loop.I'll probably do this myself in the next few days and submit a PR, but thought I should put this in to see if anyone else has thoughts on it.
The text was updated successfully, but these errors were encountered: