Overridden values from an Application CRD values block are not visualized under Parameters

[Fresa]

Checklist:

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

Describe the bug

Values from an Application CRD values block that overrides values from value files are not visualized under the App Details -> Parameters -> Parameters section.

To Reproduce

Application CRD:

project: default
source:
  repoURL: 'http://web.archive.org/web/20250607134208/https://github.com/some-repo.git'
  path: helm/charts/bootstrap
  targetRevision: master
  helm:
    valueFiles:
      - values.yaml
      - values.dev.yaml
    values: |
      test:
        foo: "hello-from-values-block"
destination:
  server: 'http://web.archive.org/web/20250607134208/https://kubernetes.default.svc'
  namespace: default
syncPolicy:
  automated: {}

values.yaml:

test:
  foo: "hello"

values.dev.yaml:

test:
  foo: "hello-dev"

helm/charts/bootstrap/templates/foo.yaml:

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: foo
  namespace: bar
  labels:
    test: {{ .Values.test.foo }}
spec:
  project: default
  source:
    chart: bar
    repoURL: https://foo.bar.io
    targetRevision: 1.2.3
  destination:
    namespace: foo
    server: https://kubernetes.default.svc

Expected behavior

Parameters 'test.foo' should read 'hello-from-values-block' not 'hello-dev'

Screenshots
Bootstrap app: App Details -> Parameters:

foo app: App Details -> Summary:

Version

v1.8.7+eb3d1fb

Logs

N/A

[jessesuen]

This is a valid bug. The application details API needs to use the same logic that the rendering does, in order to calculate projected parameters.

[Rishabhraghwendra18]

Hi @jessesuen . First timer this side . I will like to give it a try

[OliverLeighC]

any word on this?

[bmedici]

Hi, same behavior here while trying to specify 2 values-files. Sometimes the first one is taken into account, sometimes none of them.
Any news ?

[j-grims]

is there a timeline for a fix?

[mnacharov]

Hi!
It looks like a mess...

According to the api of argocd app set we have 5 options to set values which will be used to render a helm chart:

• --values
• --values-literal-file
• --helm-set
• --helm-set-string
• --helm-set-file

The first two of them are passed to the --values parameter of helm template command. --values has a priority on --values-literal-file - source code

The last three are passed to the

• --set
• --set-string
• --set-file

respectively. And according to the helm logic overrides values

In my opinion, it would be better if "Parameters" section of Argocd Application describes --set and --set-string options or in yaml - helm.parameters section:

spec:
  source:
    helm:
      parameters:
      - name: app
        value: $ARGOCD_APP_NAME

But, as I understood correctly, it historically contains output of helm inspect values - rendered values.yaml file from the helm chart and one or more --values-literal-file from argocd application - source code

So, --values, --helm-set, --helm-set-string, --helm-set-file parameters are simply ignored.

I'm going to populate Parameters from all of them, but it looks like we need one extra attribute for this logic

[brat002]

It's only UX bug. Just tap Enter after fill in values field.

[chiragbhatia8]

This is actually a pain, when trying to use the appset with individual apps ability to define the parameters, I am unable to cast parameters from string to a array when using it with argocd for below template

`
{{- $projectName := printf "%s" $.Values.argocd.project.name -}}
{{- $disableAutoSync := .Values.argocd.applicationSet.disableAutoSync | default false }}
{{- $env := .Values.argocd.environment }}
{{- $identifier := "" }}
{{- if .Values.argocd.applicationSet.identifier }}
{{- $identifier = printf "-%s" $.Values.argocd.applicationSet.identifier}}
{{- end }}
{{- if .Values.argocd.applicationSet.enabled }}
apiVersion: argoproj.io/v1alpha1
kind: ApplicationSet
metadata:
name: {{ printf "%s-%s%s-appset" .Values.argocd.project.name .Values.argocd.environment $identifier }}
namespace: {{ .Values.argocd.namespace }}
spec:
generators:
- list:
elements:
{{- range .Values.argocd.apps }}
- appName: {{ printf "%s-%s%s" $.Values.argocd.environment .name $identifier }}
namespace: {{ $.Values.argocd.environment }}
path: {{ .path }}
parameters:
{{- if .parameters }}
{{- range .parameters }}
- name: {{ .name }}
value: {{ .value }}
{{- end }}
{{- end }}
{{- end }}
template:
metadata:
name: '{{ "{{appName}}" }}'
annotations:
argocd.argoproj.io/manifest-generate-paths: .
spec:
project: {{$projectName}}-project
source:
repoURL: {{ $.Values.argocd.applicationSet.repo }}
targetRevision: main
path: '{{ "{{path}}" }}'
helm:
passCredentials: true
releaseName: '{{ "{{appName}}" }}'
valueFiles:
{{- toYaml $.Values.argocd.valueFiles | nindent 12 }}
parameters:
'{{ "{{parameters}}" }}'
destination:
name: {{ $.Values.argocd.applicationSet.destinationName }}
namespace: {{ $.Values.argocd.environment }}
syncPolicy:
{{- if eq $disableAutoSync false }}
automated:
prune: true
selfHeal: true
{{- end }}
syncOptions:
- CreateNamespace=true
- PrunePropagationPolicy=background

{{- end }}
`

Invalid value: "string": spec.template.spec.source.helm.parameters in body must be of type array: "string" (retried 2 times).

[Ruby-rc]

@nitishfy If no one is assigned to this issue，Could I continue handling this issue?

Also, I noticed that when setting the value of 'valuesObject' while editing the UI YAML, the page crashes. Should we create a new issue to follow up on this?"

apiVersion: argoproj.io/v1alpha1
kind: Application
 ...

 source:
    path: app-test
    repoURL:  ''
    targetRevision: HEAD
    path: ''
    helm:
      releaseName: test
      valuesObject:
        custom: "custom"

[Ruby-rc]

I am trying to fix this issue, but as mentioned in the #22367 (comment):

The display error in parameters involves several values' precedence problems (Order of precedence is parameters > valuesObject > values > valueFiles > Helm repository values.yaml). As shown in the figure, when editing, if the Helm parameters are as follows, what should the behavior of "Remove override" and "keepoverride" be? (Is it reasonable to directly clear the values of values, valuesObject, and parameters?)

Need to confirm whether everyone considers such UI behavior to be reasonable.