-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
feat(cmd/influx): add secret cli #16786
Conversation
82f6a5a
to
14a5804
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the only must chagne is fixing the error to match up with the domain
14a5804
to
d7b3228
Compare
d7b3228
to
670d2b7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cmd := b.newCmd("update", b.cmdUpdateRunEFn) | ||
cmd.Short = "Update secret" | ||
cmd.Flags().StringVarP(&b.key, "key", "k", "", "The secret key (required)") | ||
cmd.MarkFlagRequired("key") | ||
b.org.register(cmd, false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can pass a key, but how do you update the value of the secret?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sanderson This is done through a prompt similar to our password flow. I'm adding a card to provide it over the CLI as an arg in the same command.
cmd := b.newCmd("find", b.cmdFindRunEFn) | ||
cmd.Short = "Find secrets" | ||
b.org.register(cmd, false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is an overall critique of "find"/"list" commands throughout the influx
CLI. We are inconsistent. For some it's "list" and others it's "find". The term "find" indicates a searching action and I would expect ways to filter the results. This just lists all the secret keys.
My personal preference would be to make everything consistent and use either list
or ls
to align with standard Linux/UNIX command line tools.
@jademcgough
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sanderson, this x1000! I've had the same feelings towards list|find. I would really love to see it become list if it does not allow for filtering. We do have filtering on some Find commands, either by name or what not. But these are still akin to list operations for me in most nix envs. I would love to see list
and ls
as an alias shorthand for calling it 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@sanderson we're going to make these changes 👍. @influxdata/tools-team is on board 🤘
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Closes #16475
Add the http secret service, cli, and tests