resource.customizations is deleted from argocd-cm configmap about gitops-operator HOT 4 CLOSED

Hi @nastacio , Thanks for raising issue with us.

Operator reconciles on changes made to the argo cd resources and sets them back to default. This is an expected behaviour. Any changes that you require should be rather made as part of Argo CR.

Please add your customizations to argocd CR

cr.Spec.ResourceCustomizations

This is the piece of code which sets the argo cd config map back to default.
https://github.com/argoproj-labs/argocd-operator/blob/3aa839b023883b564ac5bfd6012f16f9ce19797b/pkg/controller/argocd/configmap.go#L437

from gitops-operator.

@iam-veeramalla your solution works, which is fantastic for our immediate needs.

There is an odd inconsistency with other patches to that same argocd-cm, since I could patch the repositories parameter without it being reset.

I can understand the need to restructure the way the configuration is managed (moving it up from the ConfigMap to the ArgoCD object), but it seems like letting some portions of argocd-cm behave like in ArgoCD (e.g. repositories can be patched and is not reset) , but not others, will confuse a lot of people familiar with ArgoCD.

from gitops-operator.

Thanks @nastacio .. I will take a look at why changes in repositories is not reset by the controller.

from gitops-operator.

Hi @iam-veeramalla,
I'm encountering the same issue as @nastacio was facing, but in the ArgoCD CR rather than the ConfigMap.
I am updating the CR, but it will occasionally reset and completely remove my resource customizations.

from gitops-operator.