a3dfde5cec
* conversion stage 1 * correct image paths * add sidebar title to frontmatter * docs/concepts and docs/internals * configuration docs and multi-level nav corrections * commands docs, index file corrections, small item nav correction * secrets converted * auth * add enterprise and agent docs * add extra dividers * secret section, wip * correct sidebar nav title in front matter for apu section, start working on api items * auth and backend, a couple directory structure fixes * remove old docs * intro side nav converted * reset sidebar styles, add hashi-global-styles * basic styling for nav sidebar * folder collapse functionality * patch up border length on last list item * wip restructure for content component * taking middleman hacking to the extreme, but its working * small css fix * add new mega nav * fix a small mistake from the rebase * fix a content resolution issue with middleman * title a couple missing docs pages * update deps, remove temporary markup * community page * footer to layout, community page css adjustments * wip downloads page * deps updated, downloads page ready * fix community page * homepage progress * add components, adjust spacing * docs and api landing pages * a bunch of fixes, add docs and api landing pages * update deps, add deploy scripts * add readme note * update deploy command * overview page, index title * Update doc fields Note this still requires the link fields to be populated -- this is solely related to copy on the description fields * Update api_basic_categories.yml Updated API category descriptions. Like the document descriptions you'll still need to update the link headers to the proper target pages. * Add bottom hero, adjust CSS, responsive friendly * Add mega nav title * homepage adjustments, asset boosts * small fixes * docs page styling fixes * meganav title * some category link corrections * Update API categories page updated to reflect the second level headings for api categories * Update docs_detailed_categories.yml Updated to represent the existing docs structure * Update docs_detailed_categories.yml * docs page data fix, extra operator page remove * api data fix * fix makefile * update deps, add product subnav to docs and api landing pages * Rearrange non-hands-on guides to _docs_ Since there is no place for these on learn.hashicorp, we'll put them under _docs_. * WIP Redirects for guides to docs * content and component updates * font weight hotfix, redirects * fix guides and intro sidenavs * fix some redirects * small style tweaks * Redirects to learn and internally to docs * Remove redirect to `/vault` * Remove `.html` from destination on redirects * fix incorrect index redirect * final touchups * address feedback from michell for makefile and product downloads
46 lines
1.9 KiB
Markdown
46 lines
1.9 KiB
Markdown
---
|
|
layout: "docs"
|
|
page_title: "KV - Secrets Engines"
|
|
sidebar_title: "Key/Value"
|
|
sidebar_current: "docs-secrets-kv"
|
|
description: |-
|
|
The KV secrets engine can store arbitrary secrets.
|
|
---
|
|
|
|
# KV Secrets Engine
|
|
|
|
The `kv` secrets engine is used to store arbitrary secrets within the
|
|
configured physical storage for Vault. This backend can be run in one of two
|
|
modes. It can be a generic Key-Value store that stores one value for a key.
|
|
Versioning can be enabled and a configurable number of versions for each key
|
|
will be stored.
|
|
|
|
## KV Version 1
|
|
|
|
When running the `kv` secrets backend non-versioned only the most recently
|
|
written value for a key will be preserved. The benefits of non-versioned `kv`
|
|
is a reduced storage size for each key since no additional metadata or history
|
|
is stored. Additionally, requests going to a backend configured this way will be
|
|
more performant because for any given request there will be fewer storage calls
|
|
and no locking.
|
|
|
|
More information about running in this mode can be found in the [K/V Version 1
|
|
Docs](/docs/secrets/kv/kv-v1.html)
|
|
|
|
## KV Version 2
|
|
|
|
When running v2 of the `kv` backend a key can retain a configurable number of
|
|
versions. This defaults to 10 versions. The older versions' metadata and data
|
|
can be retrieved. Additionally, Check-and-Set operations can be used to avoid
|
|
overwritting data unintentionally.
|
|
|
|
When a version is deleted the underlying data is not removed, rather it is
|
|
marked as deleted. Deleted versions can be undeleted. To permanently remove a
|
|
version's data the destroy command or API endpoint can be used. Additionally all
|
|
versions and metadata for a key can be deleted by deleting on the metadata
|
|
command or API endpoint. Each of these operations can be ACL'ed differently,
|
|
restricting who has permissions to soft delete, undelete, or fully remove data.
|
|
|
|
More information about running in this mode can be found in the [K/V Version 2
|
|
Docs](/docs/secrets/kv/kv-v2.html)
|