Fix marker comments for runtime object deepcopy #261
Merged
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
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.
Change log description
Fix marker comments for runtime object deepcopy.
Purpose of the change
The marker comments for runtime object deepcopy was wrongly located. As such, the runtime object deepcopy code was not generated via
operator-sdk generate k8sas expected. This change fixes the issue.What the code does
Fix location of marker comments for runtime object deepcopy so that the deepcopy code gets generated correctly.
How to verify it
operator-sdk generate k8sshould generate runtime object deepcopy code correctly.