Update KAL to support new guidance on required and optional fields #2440
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.
This enforces that all API fields are omitted when unset, and serialized correctly based on whether or not their zero value is a valid user choice.
This update aligns with updated guidance in the upstream API conventions, and downstream (see openshift/enhancements#1825)
This will remove the ability for APIs to be discoverable, by dropping omitempty, the motivation for this change is explained in the linked conventions update above.