Replies: 1 comment
-
Solved it by adding the following annotation to all argocd apps annotations:
argocd.argoproj.io/manifest-generate-paths: . |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey,
It seems like every time a webhook is called, it triggers a job in an app, where nothing has changed.
It's as if it triggers the sync on all argocd apps - i thought it would do the refresh only.
Webhook is called from bitbucket repo (push action), containing manifests for all services and apps, so whenever one of the apps changes (updates the image tag), argo applies the change to the cluster.
Job has the following annotations
(this job runs migrations on sync, but before the changes are applied)
Using argocd 7.7.3
Ideas?
Can i force argocd somehow to only do the refresh on webhook and not the sync?
Thanks,
Miran
Beta Was this translation helpful? Give feedback.
All reactions