-
Notifications
You must be signed in to change notification settings - Fork 226
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
Refactor ctclient command-line tool #900
Comments
2 tasks
mhutchinson
added a commit
that referenced
this issue
May 10, 2022
All of the parameterization to the subcommands is performed by flags. However, as the subcommands themselves are selected via normal arguments (no hyphens), this can lead to newcomers (e.g. me) believing that the log to fetch from could also be a bare argument. On something like get-entries, there was no way to know that the logname was ignored. Now, this will explode and the user gets the option to reconsider how they are specifying the parameters. e.g. `go run github.com/google/certificate-transparency-go/client/ctclient@master get-entries submariner --first 35494500 --last 35494590` looks very reasonable and returns data, but it isn't from submariner. #900
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
get-consistency-proof 100 200
instead ofget-consistency-proof --flag_for_first_size=100 --flag_for_second_size=200
.The text was updated successfully, but these errors were encountered: