Add --kube-context flag support to all helm-diff commands #850
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 PR implements support for the
--kube-contextflag across all helm-diff commands (upgrade,release,revision,rollback), providing a clean alternative to the existingHELM_KUBECONTEXTenvironment variable workaround.Changes Made
Command Support:
--kube-context stringflag to all four helm-diff commandsImplementation Details:
kubeContextfield to all command structs (diffCmd,release,revision,rollback)getRelease(),getHooks(),getRevision(),getChart(),template(),writeExistingValues()--namespaceflagUsage Examples:
Testing:
Documentation:
This enhancement improves discoverability and provides a consistent interface that matches standard helm command behavior, while maintaining backward compatibility with the existing
HELM_KUBECONTEXTenvironment variable.Fixes #603.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.