Have argoproj.io.ArgoCD to support resource customization in favor of per resource ConfigMap key

[morningspace]

Is your feature request related to a problem? Please describe.

According to the ArgoCD CRD, it's currently using resourceCustomizations to define resource customization, and this will ultimately be applied to the argocd-cm ConfigMap using resource.customizations key. However, according to this post:

In the upcoming release, the resource.customizations key has been deprecated in favor of a separate ConfigMap key per resource. This allows to decompose the Argo CD configuration and makes it more convenient to use with config management tools such as Kustomize.

Describe the solution you'd like With that, can we have argoproj.io.ArgoCD to support resource customization in favor of per resource ConfigMap key?

For those who are new to resource customization, it would be confusing to them since there are two formats. And from the latest official Argo CD documents, it has already been transformed to use the new format.

[nastacio]

Any news on this?

Seems like an important departure from the ArgoCD configuration model if they ever deprecate the (now) old format.

[prakrit55]

@iam-veeramalla, is it still open to be fixed? I wd like to do it with pleasure .