-
Notifications
You must be signed in to change notification settings - Fork 98
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
Allow consulate kv get
to return recursive listing of keys?
#56
Comments
Sounds great :) |
Cool! Quick question... This is what I've implemented:
It would be nice to offer an option similar to
Or with a shorter prefix, like this:
Do you think that this should be the default? Or should we offer a flag, like Thanks! |
I do not think it should be the default, and --trim # would be good where # defaults to 1. |
What would the number in # full keys:
# test/recursive/KEY_1
# test/recursive/KEY_2
# test/recursive/KEY_3
# default output:
$ consulate kv get -r test/recursive/
test/recursive/KEY_1 one
test/recursive/KEY_2 two
test/recursive/KEY_3 three
# trimmed output:
$ consulate kv get -r --trim test/recursive/
KEY_1 one
KEY_2 two
KEY_3 three
# trimmed output (shorter prefix specified as arg):
$ consulate kv get -r --trim test/
recursive/KEY_1 one
recursive/KEY_2 two
recursive/KEY_3 three Would this work? Thanks! |
Sure.. was just thinking that adding a default # of 1 that could be overridden would allow for
|
What do you think about adding a
-r
option toconsulate kv get
to request all keys in a given path? Like this:I'd be happy to add it to the CLI and submit a pull request, just wanted to make sure that it's a welcome contribution.
The text was updated successfully, but these errors were encountered: