Skip to content
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

-field option not supported by 'vault kv get' #4424

Closed
faudebert opened this issue Apr 23, 2018 · 0 comments
Closed

-field option not supported by 'vault kv get' #4424

faudebert opened this issue Apr 23, 2018 · 0 comments

Comments

@faudebert
Copy link

Using -field flag from vault read is quite useful to avoid calling jq when using KV secrets engine V1. It is not possible to use -field or similar option for KV secrets engine V2 (ie. vault kv get).

Environment:

  • Vault Version: Vault v0.10.0 ('5dd7f25f5c4b541f2da62d70075b6f82771a650d')
  • Operating System/Architecture: Debian GNU/Linux 8 (jessie) / x86_64

Expected Behavior:
Vault CLI returns a specific field on vault kv get --field some/path.

Actual Behavior:
Vault CLI returns following error message flag provided but not defined: -field.

Steps to Reproduce:
vault kv get -field=world secret/hello

References:
Vault documentation suggest it is possible to do so.

jefferai added a commit that referenced this issue Apr 23, 2018
briankassouf pushed a commit that referenced this issue Apr 23, 2018
* Enable `-field` in `vault kv get/put`

Fixes #4424

* Unify nil value handling

* Use preflight helper
truenorthcreative pushed a commit that referenced this issue Apr 23, 2018
* Update kv command to use a preflight check

* Make the existing ui endpoint return the allowed mounts

* Add kv subcommand tests

* Enable `-field` in `vault kv get/put` (#4426)

* Enable `-field` in `vault kv get/put`

Fixes #4424

* Unify nil value handling

* Use preflight helper

* Update vkv plugin

* Add all the mount info when authenticated

* Add fix the error message on put

* add metadata test

* No need to sort the capabilities

* Remove the kv client header

* kv patch command (#4432)

* Fix test

* Fix tests

* Use permission denied instead of entity disabled
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant