feat: schema validation update to support YAML anchors
Feature Request
Why
When upgrading to BB 2.0, we found the new helm schema validator to be broken for our YAML anchor usage:
- (root): Additional property toleration_anchors is not allowed │
- (root): Additional property okta_anchors is not allowed
The configuration additionalProperties: false
is intended to prevent wandering config and offers good value. But this is at odds with yaml anchors, because while YAML anchors create meta-references for different code blocks, the anchor definition must exist at some real level of the processed yaml. Fortunately I've been able to work around this by shoving it in the addons block for the time being, which does not have the additionalProperties set:
addons:
my_anchors:
&foo: my-foo-value
&bar: my-bar-value
Proposed Solution
A non-required field in the schema that allows for arbitrary config, be it something like "custom" or "user_specified" or something; it doesn't really matter to me:
custom:
my_anchors:
&foo: my-foo-value
&bar: my-bar-value