2b81ea64c3
* Adding vault kv command doc * Update website/source/docs/commands/kv/delete.html.md Co-Authored-By: Becca Petrin <beccapetrin@gmail.com> * Update website/source/docs/commands/kv/delete.html.md Co-Authored-By: Becca Petrin <beccapetrin@gmail.com> * Update website/source/docs/commands/kv/destroy.html.md Co-Authored-By: Becca Petrin <beccapetrin@gmail.com> * Update website/source/docs/commands/kv/destroy.html.md Co-Authored-By: Becca Petrin <beccapetrin@gmail.com> * Update website/source/docs/commands/kv/undelete.html.md Co-Authored-By: Becca Petrin <beccapetrin@gmail.com> * Update website/source/docs/commands/kv/delete.html.md Co-Authored-By: Becca Petrin <beccapetrin@gmail.com>
980 B
980 B
| layout | page_title | sidebar_title | sidebar_current | description |
|---|---|---|---|---|
| docs | kv enable-versioning - Command | <code>enable-versioning</code> | docs-commands-kv-enable-versioning | The "kv enable-versioning" command turns on versioning for the backend at the provided path. |
kv enable-versioning
The kv enable-versioning command turns on versioning for an existing
non-versioned key/value secrets engine (K/V Version 1) at its path.
Examples
This command turns on versioning for the K/V Version 1 secrets engine enabled at "secret".
$ vault kv enable-versioning secret
Success! Tuned the secrets engine at: secret/
Usage
There are no flags beyond the standard set of flags included on all commands.
Output Options
-format(string: "table")- Print the output in the given format. Valid formats are "table", "json", or "yaml". This can also be specified via theVAULT_FORMATenvironment variable.