This repository was archived by the owner on Apr 2, 2024. It is now read-only.
deploy/helm-chart: add schema for input validation #1551
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1d1acb8 to
f76fb26
Compare
Schema was generated using https://jsonschema.net/. More information on schema generation can be found in https://www.arthurkoziel.com/validate-helm-chart-values-with-json-schemas/ Signed-off-by: Paweł Krupa (paulfantom) <pawel@krupa.net.pl>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Schema was generated using https://jsonschema.net/. More information
on schema generation can be found in https://www.arthurkoziel.com/validate-helm-chart-values-with-json-schemas/
Description
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Note: If your PR involves benchmarks, you can run the
Benchmarksworkflow by addingaction:benchmarkslabel. The PR must be opened from Promscale branch so that Github actions can leave a comment comparing results againstmaster.Merge requirements
Please take into account the following non-code changes that you may need to make with your PR: