Proposed Feature
Kargo's existing argocd-update step supports modifying the app spec of the live application, e.g. to update source revision, etc... This is in addition to it's ability to simply sync an app.
For those who are practicing a traditional GitOps process that is syncing from the tip of a branch, users may benefit from a simpler argocd-sync step, which simply syncs the app but does not allow updates to it.
Motivation
argocd-update has been a source of confusion. You can say it does too much. Having a simpler primitive would make things easier for folks to understand. It would also model how the argocd CLI works in CI pipelines.
Proposed Feature
Kargo's existing
argocd-updatestep supports modifying the app spec of the live application, e.g. to update source revision, etc... This is in addition to it's ability to simply sync an app.For those who are practicing a traditional GitOps process that is syncing from the tip of a branch, users may benefit from a simpler
argocd-syncstep, which simply syncs the app but does not allow updates to it.Motivation
argocd-updatehas been a source of confusion. You can say it does too much. Having a simpler primitive would make things easier for folks to understand. It would also model how the argocd CLI works in CI pipelines.