-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--tls-allow-insecure breaks argument parsing #711
Comments
Thanks for your feedback, the right way:
Don't use any flags before subcommand, because these flags are registered in subcommand, you can see the common flags from root command.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When passing
--tls-allow-insecure
in a command like:We get an error.
In the help, it doesn't seem like you need
-tls-allow-insecure true
but if you don't include the true, and do the following:The
--tls-allow-insecure
is chomping the next argumentThe following does work:
But it is pretty awkward.
The text was updated successfully, but these errors were encountered: