nebari-dev / nebari-dev/rayserve-pack
rendered chart is never checked for correctness in CI
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1
- Forks
- 4
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 5
Description
Surfaced in https://github.com/nebari-dev/rayserve-pack/pull/38/changes#r3881960421.
All three steps just run helm template, which only fails if the output is not valid YAML. It doesn't assert anything about the output being correct.
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
Start with .github/workflows/lint.yaml at lines 24-42 and inspect the three helm template steps. Determine how the rendered chart should be checked beyond valid YAML, then add CI validation for the expected output. Done means the workflow detects an incorrect rendered chart, not only malformed YAML.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100