improvement: remove kubeconfig inputs #11
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
The Kubeconfig inputs turned out to confuse some of our users. Let's move the responsibility to set up the Kubeconfig to the user, just like we do with Garden itself. This makes the action easier to understand if you already know how to use Garden. See also https://discord.com/channels/817392104711651328/1245455859694178334
twelvemo
approved these changes
Jun 11, 2024
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.
BREAKING CHANGE:
The Kubeconfig inputs turned out to confuse some of our users. Let's move the responsibility to set up the Kubeconfig to the user, just like we do with Garden itself. This makes the action easier to understand if you already know how to use Garden.
See also https://discord.com/channels/817392104711651328/1245455859694178334