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.
Hi,
At my workplace, we use regex matches in tpls to match for values in the root of the values.yaml. I saw the helm-schema doesn't support such a usecase, but since json-schema supports it i decided to implement it myself.
I added a new field to the schema, keyAsPatternProperty that allows matching all keys on the same level to a certain regex pattern (that is provided in the schema)
I struggled a bit in figuring out whether it's better for the field to be boolean (and take the yaml-key as the pattern to match on) or string, but I decided it would probably foot-gun someone to have a mangled key instead of some arbitrary, very unlikely to match key.
Here's and example usage
boolean:
string:
Thanks in advance 😊
P.S: I see that the README's table changed, but it's only formatting (the only real change is the addition of the keyAsPatternProperty)