The config statusbadge.enabled expects a boolean instead of a string about argo-helm HOT 1 OPEN

In response to: #2870 (comment)

I understand the result is OK, that is not the argument here. The result is OK because we cast all values to strings here: https://github.com/argoproj/argo-helm/blob/main/charts/argo-cd/templates/_helpers.tpl#L202

However, at the VALUES, all values were converted to bools:

configs:
  cm:
    server.rbac.log.enforce.enable: false
    exec.enabled: false
    admin.enabled: true
    statusbadge.enabled: false

Since the user may fill these in as strings, as expected by ArgoCD's documentation, the change in da00680 caused breakage.

What I am arguing is that this is unexpected. When I look at these values, I think they will map DIRECTLY to ArgoCD's CM: https://argo-cd.readthedocs.io/en/stable/operator-manual/argocd-cm-yaml/

It "looks like it does", and it in fact, it does, but we cast all values to strings. So, suddenly requiring the user to fill out a bool instead of a string is "unexpected". This caused breakage when updating (in my use case) and also the one reported in #2663.

from argo-helm.