We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Several folks and I have been hit by this issue:
notation sign --key=$KEY_NAME $IMAGE
notation sign $IMAGE --key=$KEY_NAME
signing key not found
The same problem applies to any non-required flag which is used together with an argument, i.e. -p/-u.
-p/-u
Using flags after arguments seems not to be supported by urfave/cli, see urfave/cli#976.
urfave/cli
We should at least error early with a meaningful message instead of executing the normal workflow and having a random error message.
@dtzar
The text was updated successfully, but these errors were encountered:
+1. I realize the positional parameter shouldn’t have named parameters after. I like the idea of an error, not even a warning.
Sorry, something went wrong.
Let's move to github.com/spf13/cobra.
github.com/spf13/cobra
I will take a look at it.
Yes, this would be great! It would also help with the user experience because of the autogenerated help and man pages.
chloeyin
Successfully merging a pull request may close this issue.
Several folks and I have been hit by this issue:
notation sign --key=$KEY_NAME $IMAGE
worksnotation sign $IMAGE --key=$KEY_NAME
does not works and errors out withsigning key not found
.The same problem applies to any non-required flag which is used together with an argument, i.e.
-p/-u
.Using flags after arguments seems not to be supported by
urfave/cli
, see urfave/cli#976.We should at least error early with a meaningful message instead of executing the normal workflow and having a random error message.
@dtzar
The text was updated successfully, but these errors were encountered: