Open felipecrs opened 1 week ago
Wow, this is nasty. And it doesn't look like there is a proper workaround, except exposing werf
values at $.Values.global.werf
. Additionally, for now we can just print a warning if this specific error (Additional property werf is not allowed
) occured, without failing the deployment.
We need to think on it.
Maybe you can hack into the function that calls this validation, and patch the schema to add the werf property before actually validating.
Yea, maybe, I'm just afraid how complex these schemas can be and how patchable are they.
Before proceeding
Version
2.13.1
How to reproduce
Result
See above.
Expected result
To work, as it works without
werf
.Additional information
No response