[codegen] Don't Generate Go Metadata Type #1094
Open
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.
What Changed? Why?
[codegen] Allow GoTypes Jenny to have a configurable set of fields to exclude from generation when Depth > 0, and exclude the metadata field from generation using this behavior in the go resource generator. The
metadatatype is not used and can cause confusion for users, as it is a merge of the kubernetes object metadata and the custom metadata fields which are set as annotations in the actual object type. It was previously generated for compliance with the Thema model, which is no longer an option when generating code.How was it tested?
Tested with
make generatein a test project, as well as updating the existing unit tests.Where did you document your changes?
Updated the tutorial doc to remove references to the metadata type, as that appears to be the only place it's referenced.
Notes to Reviewers