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, if we turn off auto-healing, it won't prevent auto-healing if somebody makes a commit. Once the commit occurs, the auto-syncing does everything including auto-healing.
Scenario: If auto heal is off, I'm a user, and I manually update my Deployment resource in the cluster but then I change my ConfigMap spec in github, I want my ConfigMap to get updated but I don't want my Deployment to be auto-healed.
Edit: I just spoke to someone from ArgoCD who says the behavior actually does match our current behavior (although they also have an option of doing a Partial Sync manually I guess). So, I've listed this as an enhancement instead.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
@xdevxy I changed this to "enhancement" as you imagined it should be. I just spoke to someone from ArgoCD who says the behavior actually does match our current behavior (although they also have an option of doing a Partial Sync manually I guess).
Describe the enhancement
Currently, if we turn off auto-healing, it won't prevent auto-healing if somebody makes a commit. Once the commit occurs, the auto-syncing does everything including auto-healing.
Scenario: If auto heal is off, I'm a user, and I manually update my Deployment resource in the cluster but then I change my ConfigMap spec in github, I want my ConfigMap to get updated but I don't want my Deployment to be auto-healed.
Edit: I just spoke to someone from ArgoCD who says the behavior actually does match our current behavior (although they also have an option of doing a Partial Sync manually I guess). So, I've listed this as an enhancement instead.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: