Fix plugin argument parsing after kube TLS boolean flag - #32526
Open
ulofiai wants to merge 1 commit into
Open
Conversation
Signed-off-by: ulofiai <monsterking@tutamail.com>
pull-request-size
Bot
added
the
size/M
github-actions
Bot
added
the
v4.x
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.
Fixes #13686.
Treat
--kube-insecure-skip-tls-verifyas an optional-value boolean while separating Helm flags from plugin arguments. A bare flag no longer consumes the following plugin flag, while explicit separated boolean values are normalized to--flag=valuefor compatibility.Adds focused regression coverage for bare, separated-value, and inline-value forms.