Any way to prevent ArgoCD mutations?

[b-jkchen]

Hey folks, I'd ask this question on Slack but my company has it blocked :(

I'm looking for a way to prevent the ArgoCD webhooks from mutating ArgoCD resources. My use case is that I'm deploying Big Bang and trying to integrate its deployment of ArgoCD with its deployment of GitLab. Every time I attempt to create an Application or Repository on ArgoCD to point to GitLab, Zarf automatically mutates them to point to the Zarf Gitea instead.

I've looked through the Helm values for ArgoCD to try and apply the zarf.dev/agent: ignore label in the right spots, but the only thing I've found was the ability to apply that label to all ArgoCD resources (resulting in it breaking upon initial deployment), or to all ArgoCD CRDs (which still does not appear to prevent Applications from being mutated, and does not impact Repository configs stored as Secrets).

Am I missing something obvious here? I feel like it should be straightforward to apply the labels in the right spots. The workaround I'm using right now is to edit the Zarf MutatingWebhookConfiguration to remove the ArgoCD webhooks, which is obviously not ideal. Though an alternate way to solve this problem is to introduce the ability to selectively deploy webhooks on init (unless that's already possible and I missed that feature too).

Edit for those that may have the same question: If you need to upgrade Zarf in the cluster, add the zarf.dev/agent=ignore label on your ArgoCD namespace before running zarf init. Once the init package is deployed, remove the ArgoCD webhooks, then remove the label.