feat: add custom kubeconfig option as action input#119
Merged
Conversation
Signed-off-by: Jonathan Battiato <[email protected]>
1 task
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
2 participants
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.
Adding the custom
kubeconfigoption to pass it as an action input allows anyone to specify a certainKUBECONFIGenvironment variable to be used along the entire workflow job.E.G.: I had to create a
kindcluster to run some commands. This command requires the$KUBECONFIGto contain the actual kubernetes config path. With this patch I'm allowed to export the variable required to the next steps with certainty that I'm using the right kubernetes config.