Linting tests should include linting the rendered yaml from the helm templates
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go Template
- Stars
- 534
- Forks
- 314
- Avg merge
- 42m
- Merged PRs (30d)
- 1
Description
@kabakaev had a good suggestion about linting the rendered yaml during the testing actions.
- The github actions should perform a lint test on the rendered helm templates.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the repository's GitHub Actions workflows and Helm templates to find the existing testing entry point. Run the current workflow or its local equivalent, then add rendered-template linting so the action verifies valid YAML from the Helm output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, helm, kubernetes
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100