helm valuesObject does not work

[babelfish]

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

I was trying to add some values overrides to the keda helm chart. I tried to use source.helm.valuesObject which, according to the docs, seemed to be exactly what I needed, but after syncing the Application definition, the app still showed as fully in sync. It was not using the values I provided when rendering the chart's templates. I could see the values I provided shown in the Parameters tab of the app details, however it was still rendering the templates with the default values from the chart's values.yml.

When I switch it to use source.helm.values instead, it immediately worked.

To Reproduce

Create an Application that uses source.helm.valuesObject to try to pass values to a helm chart.

This does not work:

source:
  repoURL: https://github.com/kedacore/charts
  path: keda
  targetRevision: v2.15.1
  helm:
    valuesObject:
      podIdentity:
        gcp:
          enabled: true
          gcpIAMServiceAccount: [redacted].iam.gserviceaccount.com
destination:
  server: https://kubernetes.default.svc
  namespace: keda
syncPolicy:
  syncOptions:
    - CreateNamespace=true

This does work:

source:
  repoURL: https://github.com/kedacore/charts
  path: keda
  targetRevision: v2.15.1
  helm:
    values: |
      podIdentity:
        gcp:
          enabled: true
          gcpIAMServiceAccount: [redacted].iam.gserviceaccount.com
destination:
  server: https://kubernetes.default.svc
  namespace: keda
syncPolicy:
  syncOptions:
    - CreateNamespace=true

Expected behavior

Values provided via source.helm.valuesObject should work the same as via source.helm.values.

Screenshots

Version

argocd: v2.13.1+af54ef8
  BuildDate: 2024-11-20T15:58:16Z
  GitCommit: af54ef8db5adfa77a08d4d05b1318a2198084c22
  GitTreeState: clean
  GoVersion: go1.23.1
  Compiler: gc
  Platform: linux/amd64

Upgrading argo is outside of the scope of what I'm currently working on, so I can't test with the latest version, but I did look through the changelogs of more recent releases and didn't see any reference to this.

Logs

n/a