From 049e7928b649542002df82ec04a8a32af6b77b2d Mon Sep 17 00:00:00 2001 From: Kelly Date: Mon, 9 Sep 2019 16:14:31 -0700 Subject: [PATCH] move note about kv-v2 up to install section --- content/v2.0/security/secrets/use-vault.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/v2.0/security/secrets/use-vault.md b/content/v2.0/security/secrets/use-vault.md index 7b6a74b60..e50ff4716 100644 --- a/content/v2.0/security/secrets/use-vault.md +++ b/content/v2.0/security/secrets/use-vault.md @@ -33,6 +33,14 @@ For this example, install Vault on your local machine and start a Vault dev serv vault server -dev ``` +{{% note %}} +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) @@ -125,14 +133,6 @@ 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/` -{{% note %}} -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`. - Secrets are stored in Vault as key value pairs in their respective secrets engines. ```