You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add an ability to show full manifest of a helm chart before it gets applied, with an option to see it even if it's invalid (maybe even add a basic linter to it to debug even faster?)
Motivation
Sometimes you might make a mistake in making own helm chart (f.e. push to repo and don't test locally - actually happens if you have to work from a different computer) and get a long unreadable error message from ArgoCD that something is invalid, usually taking whole screen space, going out of bounds in UI, and etc.
Proposal
It would be nice to have an option to see full manifest of an object even if yaml has errors in it (e.g. as in helm template --debug). Or have a button to "debug" template with a specific values file before creation, getting full list of objects to be applied later.
The text was updated successfully, but these errors were encountered:
This is not easily doable because the API between repo-server and api-server expects well-formatted JSON, which does not support showing the raw rendered output of the tooling
Summary
Add an ability to show full manifest of a helm chart before it gets applied, with an option to see it even if it's invalid (maybe even add a basic linter to it to debug even faster?)
Motivation
Sometimes you might make a mistake in making own helm chart (f.e. push to repo and don't test locally - actually happens if you have to work from a different computer) and get a long unreadable error message from ArgoCD that something is invalid, usually taking whole screen space, going out of bounds in UI, and etc.
Proposal
It would be nice to have an option to see full manifest of an object even if yaml has errors in it (e.g. as in
helm template --debug
). Or have a button to "debug" template with a specific values file before creation, getting full list of objects to be applied later.The text was updated successfully, but these errors were encountered: