Clarify metadata processing in pod resource overrides #3613
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By using reflection, instead of a per-struct GetMetadata() method for each override struct that we define, it becomes much easier to see that the logic is to apply labels and annotations from the struct's Metadata field, so long as the struct _has_ that field.
nelljerram
added
release-note-not-required
docs-not-required
and removed
docs-pr-required
release-note-required
labels
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
By using reflection, instead of a per-struct GetMetadata() method for each override struct that we define, it becomes much easier to see that the logic is to apply labels and annotations from the struct's Metadata field, so long as the struct has that field.