ArgoCD ignores every "enabled" in values.yaml file other than "global.enabled" when including Hashicorp Vault in ArgoCD

[denrobin]

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

When I create an application in ArgoCD to manage my vault in Kubernetes and refer to my edited values.yaml file, it only recognizes global.enabled while ignoring every other enabled configuration.

To Reproduce

1. Install Hashicorp Vault into Kubernetes through helm.
2. Create a repository for Hashicorp Vault. Use the "App of Apps" pattern.
3. In the values.yaml file, set global.enabled to "false" and some of the enabled keys to "true" or vice versa.
4. Add Hashicorp Vault and its repository to ArgoCD.

Expected behavior

ArgoCD prioritizes the values of the "enabled" keys and only defaults to "global.enabled" if the value is "-".

Screenshots

There i configured "global.enabled" to true and "injector.enabled" to false.

This is the result of "global.enabled" to false and "server.enabled" to true

Version

helm version of vault: 0.29.1
ArgoCD: v2.12.1
helm in ArgoCD: v3.15.2
helm (Client): v3.16.3

[rumstead]

Without knowing the setup of your helm chart, it sounds like you have a parent chart with some subcharts. Eg, vault.server.enabled

https://helm.sh/docs/chart_template_guide/subcharts_and_globals/#overriding-values-from-a-parent-chart

if you perform a helm template with your overrides do you get the expected manifests?