f3df55ad58
* Adding check-legacy-links-format workflow * Adding test-link-rewrites workflow * Updating docs-content-check-legacy-links-format hash * Migrating links to new format Co-authored-by: Kendall Strautman <kendallstrautman@gmail.com>
34 lines
878 B
Plaintext
34 lines
878 B
Plaintext
---
|
|
layout: docs
|
|
page_title: kv enable-versioning - Command
|
|
description: |-
|
|
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".
|
|
|
|
```shell-session
|
|
$ vault kv enable-versioning secret
|
|
Success! Tuned the secrets engine at: secret/
|
|
```
|
|
|
|
## Usage
|
|
|
|
There are no flags beyond the [standard set of flags](/vault/docs/commands)
|
|
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 the
|
|
`VAULT_FORMAT` environment variable.
|