Bad parameters retrieved for Helm files in UI and Notifications

[paydaycay]

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

Since v2.3.3 (I was in 2.2.5 before and didn't get the problem), values retrieved from Helm file in the UI are not the good ones.
The values retrieved are the default values and not the ones in my overlay file.

For example, In my default value file, I have php.image.tag equals to "helm".
The override value in my overlay file for php.image.tag is equal to "test-XXXXX".

I retrieve "helm" instead of "test-XXXXX".

I encounter the same problem in ArgoCD Notifications when I attempt to retrieve a value from Helm file in my templates.

To Reproduce

Just create a Helm chart and create an overlay file to override the default values. When you click on the application in the interface and go to "Parameters" tab, you will see the default values and not the good ones.

With ArgoCD Notifications, you can retrieve it by calling this :

{{ (call .repo.GetAppDetails).Helm.GetParameterValueByName "php.image.tag" }}

And you won't retrieve the correct ones.

Expected behavior

I expect to retrieve the correct values that are in my overlay file as it was in v2.2.5.

Screenshots

In the UI :

In the values.yaml default file :

In the test.yaml overlay file :

Part of my notifications template :

Part of the notification received :

Version

argocd: v2.3.3+07ac038
  BuildDate: 2022-03-30T00:06:18Z
  GitCommit: 07ac038a8f97a93b401e824550f0505400a8c84e
  GitTreeState: clean
  GoVersion: go1.17.6
  Compiler: gc
  Platform: linux/amd64

Logs

No relevant logs found.

[uniit]

+1 Please prioritize this one b/c it misleads many people when they see different values on the parameters page and deployed applications. Otherwise please recommend a correct way how to use helm overrides in Argo.

[mihma]

Similar issue after upgrading to 2.3.3. Is there a work around it?

[sgavrylenko]

have the same problem

[fredfp]

this seems to be a duplicate of #8808

[crenshaw-dev]

Agreed, duplicate. Thanks for reporting!

[crenshaw-dev]

Yuck, I dislike GitHub's phrasing. It is planned, it's just a duplicate. :-P