Output full paths to files with errors from lint

[tillig]

I'm trying to create a problem matcher for VS Code such that I can include helm lint as part of the build for a chart repo and have problems tied back to actual files.

Right now when helm lint finds a problem, it outputs locations of problems in a sort of relative way:

$ helm lint
==> Linting .
[ERROR] Chart.yaml: version is required
[INFO] Chart.yaml: icon is recommended
[ERROR] templates/: validation: chart.metadata.version is required
[ERROR] : unable to load chart
	validation: chart.metadata.version is required

Error: 1 chart(s) linted, 1 chart(s) failed

In order to actually indicate the file that is built, you end up needing to put three things together:

• The current folder (in case you didn't pass in a path or passed in a relative path)
• The message from the linter (==> Linting _____)
• The name of the file after [ERROR] or [INFO]

That's not terribly easy to do from an automated build "find the file based on a regex match" sort of thing.

It would be nice if the helm lint messages could optionally output an absolute path to the file with the issue, something like:

$ helm lint --full-paths
==> Linting /Users/myname/path/to/chart/
[ERROR] /Users/myname/path/to/chart/Chart.yaml: version is required
[INFO] /Users/myname/path/to/chart/Chart.yaml: icon is recommended
[ERROR] /Users/myname/path/to/chart/templates/: validation: chart.metadata.version is required
[ERROR] : unable to load chart
	validation: chart.metadata.version is required

Error: 1 chart(s) linted, 1 chart(s) failed

If that was the case, you could very easily create a plugin problem matcher to integrate helm lint into an IDE like VS Code.

[joejulian]

See also #11357

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

[tillig]

Still an issue.

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

[tillig]

Still am issue.

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

[tillig]

Still an issue.

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

[tillig]

Still an issue.

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.

[Bhargav-InfraCloud]

/reopen