Description of problem:

• Customer is requesting clarity on the following:
• - Please provide an option to disable or pause ArgoCD sync
• - - ArgoCD sync needs to be:
• - - - 1. Optionally disable system wide
• - - - 2. Optionally disable on per cluster
• Background:
• - This is related to the mess that was cleaned up in parent case 03786217.
• - - User logged into ArgoCD UI as 'kube-admin' and went to sync cluster around 12:40UTC
• - - The operation was failing
• - - They attempted to enable the 'prune' and 'force' buttons in the ArgoCD UI for sync and still failed
• - - Then they enabled 'replace' option and synced [1] and it "worked"
• - - Once done, this begun the process to re-provision the OCP clusters managed by Gitops+ZTP+ACM because 'replace' with 'force' will delete the object and re-create it
• - - This appears to be user-error and they [Mavenir] has claimed to have lost 6 months worth of data.
• Relevant slack threads/channels:
• - https://redhat.enterprise.slack.com/archives/C06T78X8KU5
• - https://redhat-internal.slack.com/archives/C0125U6EZRS/p1712588183226619
• - https://redhat-internal.slack.com/archives/C05LM8QEB88/p1712593100181769

[1] https://kubernetes.io/docs/tasks/manage-kubernetes-objects/imperative-config/#how-to-update-objects

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

 # <steps>

Actual results:

Expected results:

Reproducibility (Always/Intermittent/Only Once):

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

 *