You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
* 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
Using
-field
flag fromvault read
is quite useful to avoid callingjq
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:
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.
The text was updated successfully, but these errors were encountered: