carvel-dev / carvel-dev/kapp-controller
Package Authors should be able to validate their packages locally
- Dominant language
- Go
- Stars
- 323
- Forks
- 127
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 4
Description
**Describe the problem/challenge you have**
I'm building a PackageRepository image bundle containing several Packages in it locally. I would like to have a way to verify that all of them are correct before pushing the bundle to a registry and deploying them into my cluster.
**Describe the solution you'd like**
I would like to have a command line that I could execute locally to verify that the contents I've just created are valid and that when deploying them to the cluster I won't face any kind of syntax error.
**Potential list of things to validate**
- Validation of the structure of the CRs such as PackageMetadata CR and Package CR
- Optional validation on the recommended metadata for packages that go in PackageMetadata CR or the Package CR. (such as icon, description, categories, release notes, etc.) [Refer to #307]
- Before pushing a package repository bundle, validate the recommended directory structure
---
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
Contributor guide
Assessment
This issue has not been assessed yet.