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
One common-ish use case for an ArgoCD Application's lifecycle is to turn off auto-sync and set / patch the kustomize image (version) by either CI/CD or by the developer itself through the CLI or API. #1843 (comment)
In case there is a set of apps that always share the same version, it makes sense to put them into an ApplicationSet, but there is no easy way to update the version of them from CLI with one command.
Something along the lines of the following would be nice.
argocd app patch [ID] --patch= /spec/generator/...
# or
argocd app set [ID] set ... [generator specific] [or something else, maybe a kustomize generator]
Maybe there is also an easier or more idiomatic solution.
With this, at least someone with access to the repo or kubectl can update the version at once, but not through the API or CLI. The CI/CD would also have to fire number of 2n times service in applicationset requests. 2n, because one patch, one sync.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
One common-ish use case for an ArgoCD Application's lifecycle is to turn off auto-sync and set / patch the kustomize image (version) by either CI/CD or by the developer itself through the CLI or API. #1843 (comment)
In case there is a set of apps that always share the same version, it makes sense to put them into an ApplicationSet, but there is no easy way to update the version of them from CLI with one command.
Something along the lines of the following would be nice.
Maybe there is also an easier or more idiomatic solution.
Example ApplicationSet
With this, at least someone with access to the repo or kubectl can update the version at once, but not through the API or CLI. The CI/CD would also have to fire number of 2n times service in applicationset requests. 2n, because one patch, one sync.
Beta Was this translation helpful? Give feedback.
All reactions