The Vault website is being redesigned to help you find what you are looking for more effectively.
kv put command writes the data to the given path in the K/V secrets
If working with K/V v2, this command creates a new version of a secret at the specified location. If working with K/V v1, this command stores the given secret at the specified location.
Regardless of the K/V version, if the value does not yet exist at the specified path, the calling token must have an ACL policy granting the "create" capability. If the value already exists, the calling token must have an ACL policy granting the "update" capability.
Writes the data to the key "creds":
$ vault kv put -mount=secret creds passcode=my-long-passcode
The data can also be consumed from a file on disk by prefixing with the "@" symbol. For example:
$ vault kv put -mount=secret foo @data.json
Or it can be read from stdin using the "-" symbol:
$ echo "abcd1234" | vault kv put -mount=secret foo bar=-
There are no flags beyond the standard set of flags included on all commands.
(string: "")- Print only the field with the given name. Specifying this option will take precedence over other formatting directives. The result will not have a trailing newline making it ideal for piping to other processes.
(string: "table")- Print the output in the given format. Valid formats are "table", "json", or "yaml". This can also be specified via the
(int: 0)- Specifies to use a Check-And-Set operation. If not set the write will be allowed. If set to 0 a write will only be allowed if the key doesn’t exist. If the index is non-zero the write will only be allowed if the key’s current version matches the version specified in the cas parameter. The default is -1.
(string: "")- Specifies the path where the KV backend is mounted. If specified, the next argument will be interpreted as the secret path. If this flag is not specified, the next argument will be interpreted as the combined mount path and secret path, with /data/ automatically inserted for KV v2 secrets.