Add clean_metadata option to resource tools for stripping verbose metadata#846
Draft
edcdavid wants to merge 1 commit intocontainers:mainfrom
Draft
Add clean_metadata option to resource tools for stripping verbose metadata#846edcdavid wants to merge 1 commit intocontainers:mainfrom
edcdavid wants to merge 1 commit intocontainers:mainfrom
Conversation
…adata Introduce a clean_metadata boolean parameter on resources_get and resources_list that strips managedFields, resourceVersion, uid, generation, and the last-applied-configuration annotation from output. This reduces token consumption and lets LLMs focus on the diagnostically relevant spec/status fields. Refactor MarshalYaml to accept functional options, replacing the previous hard-coded SetManagedFields(nil) with an opt-in WithCleanMetadata() option that performs a more thorough cleanup. Assisted by: Cursor
This file contains hidden or 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
1 participant
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.
Introduce a clean_metadata boolean parameter on resources_get and resources_list that strips managedFields, resourceVersion, uid, generation, and the last-applied-configuration annotation from output. This reduces token consumption and lets LLMs focus on the diagnostically relevant spec/status fields.
Refactor MarshalYaml to accept functional options, replacing the previous hard-coded SetManagedFields(nil) with an opt-in WithCleanMetadata() option that performs a more thorough cleanup.
Assisted by: Cursor