fix: list generator elements should be optional (cherry-pick #17424) #17511
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.
Cherry-picked fix: elements should be optional (#17424)
A bug was reported, where an applicationset with an empty elements
array, when created with
argocd appset create <filename>.yaml
gets a...list.elements: Required value
error.My hypothesis is that when calling the K8s API, golang JSON marshalling
mangles the empty
elements
array tonil
, rather than creating anempty array when submitting the
POST
.Still need to figure out why the same setup seemingly works fine when
the same appset is in an app-of-apps.
Signed-off-by: Blake Pettersson [email protected]