From 9123ee349b996b52c902b4963fdcd780c5b8fc2e Mon Sep 17 00:00:00 2001 From: Kelly Date: Mon, 9 Sep 2019 16:21:01 -0700 Subject: [PATCH] add note to enable kv-v2 -secrets storage section --- content/v2.0/security/secrets/use-vault.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/content/v2.0/security/secrets/use-vault.md b/content/v2.0/security/secrets/use-vault.md index e50ff4716..dd2fdc65a 100644 --- a/content/v2.0/security/secrets/use-vault.md +++ b/content/v2.0/security/secrets/use-vault.md @@ -37,10 +37,6 @@ vault server -dev The InfluxDB API supports KV engine v2 only. {{% /note %}} -#### Enable KV secrets engine v2 - -To pass the correct version of the KV secrets engine when you enable a secrets engine, run: `vault secrets enable kv-v2`. - ## Define Vault environment variables Use [Vault environment variables](https://www.vaultproject.io/docs/commands/index.html#environment-variables) @@ -133,8 +129,11 @@ curl --request GET \ For each organization, InfluxDB creates a [secrets engine](https://learn.hashicorp.com/vault/getting-started/secrets-engines) using the following pattern: `/secret/data/` -Secrets are stored in Vault as key value pairs in their respective secrets engines. +{{% note %}} +When you create a secrets engine, enable the `kv-v2` version by running: `vault secrets enable kv-v2`. +{{% /note %}} +Secrets are stored in Vault as key value pairs in their respective secrets engines. ``` /secret/data/031c8cbefe101000 -> this_key: foo