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
Currently, progressive sync is configured in application-set resource and it does not have any UI option to disable or pause it unlike auto-sync. It will be great if UI have an button that you can click to temporarily pause progressive-sync.
What change you think needs making.
Add either an "active" boolean field or "status" enum with options (active, paused) field in .spec.strategy of applicationset. If status is paused then argocd wont trigger out of sync apps. UI can be updated to have an option to toggle that field.
Motivation
Sometimes, we need to pause progressive-sync of applications temporarily to avoid auto deploy of high-risk changes, during maintenance or during an on-going incident. Only option to do it right now is to remove strategy block from application-set manifest and deploy it, that might not be convenient in such scenarios.
Proposal
As specified above.
How do you think this should be implemented?
The text was updated successfully, but these errors were encountered:
Summary
Currently, progressive sync is configured in application-set resource and it does not have any UI option to disable or pause it unlike auto-sync. It will be great if UI have an button that you can click to temporarily pause progressive-sync.
What change you think needs making.
Add either an "active" boolean field or "status" enum with options (active, paused) field in .spec.strategy of applicationset. If status is paused then argocd wont trigger out of sync apps. UI can be updated to have an option to toggle that field.
Motivation
Sometimes, we need to pause progressive-sync of applications temporarily to avoid auto deploy of high-risk changes, during maintenance or during an on-going incident. Only option to do it right now is to remove strategy block from application-set manifest and deploy it, that might not be convenient in such scenarios.
Proposal
As specified above.
How do you think this should be implemented?
The text was updated successfully, but these errors were encountered: