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
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.
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
-
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