mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-14 10:37:00 +02:00
Added clarification to KV documentation about default CLI behavior and how to preserve non-string type values (#3596)
This commit is contained in:
parent
4e69240ad2
commit
d3a2844a75
@ -19,6 +19,8 @@ of these backends at different mount points as you like.
|
|||||||
Writing to a key in the `kv` backend will replace the old value;
|
Writing to a key in the `kv` backend will replace the old value;
|
||||||
sub-fields are not merged together.
|
sub-fields are not merged together.
|
||||||
|
|
||||||
|
Key names must always be strings. If you write non-string values directly via the CLI, they will be converted into strings. However, you can preserve non-string values by writing the key/value pairs to Vault from a JSON file or using the HTTP API.
|
||||||
|
|
||||||
This backend honors the distinction between the `create` and `update`
|
This backend honors the distinction between the `create` and `update`
|
||||||
capabilities inside ACL policies.
|
capabilities inside ACL policies.
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user