Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom values file isn't showed in the parameters #9380

Closed
XDavidT opened this issue May 12, 2022 · 1 comment · Fixed by #9566
Closed

Custom values file isn't showed in the parameters #9380

XDavidT opened this issue May 12, 2022 · 1 comment · Fixed by #9566
Labels
bug Something isn't working

Comments

@XDavidT
Copy link

XDavidT commented May 12, 2022

Checklist:

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

Describe the bug

I've added new app, but used custom values file and not default one, and in the option, the autocomplete show me the file, and then selected. but after it's selected not change in the parameters, the parameters keep showing the default values file, even after save.

To Reproduce

  • create new app
  • click on 'app details'
  • go over parameters tab
  • click edit
  • select values file (that isn't the default)

Expected behavior

See the relevant parameters in the inputs

Version

argocd: v2.3.3+07ac038
  BuildDate: 2022-03-30T01:46:59Z
  GitCommit: 07ac038a8f97a93b401e824550f0505400a8c84e
  GitTreeState: clean
  GoVersion: go1.17.6
  Compiler: gc
  Platform: linux/amd64
argocd-server: v2.3.3+07ac038

extra info:
After looking in desired manifest it's been use the costumed values file, but it's not showed in the parameters.

Here's photo of argocd parameters I see: https://ibb.co/GkxQB68
Here's the code, that actually need to be in the parameters: https://ibb.co/s31Fh5t

@XDavidT XDavidT added the bug Something isn't working label May 12, 2022
@XDavidT
Copy link
Author

XDavidT commented Jun 15, 2022

Great - working after upgrade to 2.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants