feat: CEL validation of valuesFrom object ensuring refs are defined #1729
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.
The
valuesFrom[*].valuefrom
field onGrafanaContactPoint
can be an empty{}
resulting in nil errors in the log when reconciling.I personally ran into this when I missed a capital
K
insecretKeyRef
by mistake and Kubernetes dropped the field once applied.The following test resources are perfectly valid but the last
GrafanaContactPoint
will trigger a panic.Expand...
With this change, a validation error will be presented instead:
The GrafanaContactPoint "invalid-ref" is invalid: spec.valuesFrom[0].valueFrom: Invalid value: "object": Either configMapKeyRef or secretKeyRef must be set
Test resources:
The reason for maxItems marker
I ran into the following test error without it: