From 7aef98e04523d5eff0ceddf59f5a621f98d6be7e Mon Sep 17 00:00:00 2001 From: Scott Miller Date: Mon, 4 Apr 2022 17:03:49 -0500 Subject: [PATCH] Subtle docs change for allow_store_key (#14889) * Subtle docs change for allow_store_key * errant space --- website/content/api-docs/system/managed-keys.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/api-docs/system/managed-keys.mdx b/website/content/api-docs/system/managed-keys.mdx index 3b626349c5..749538734a 100644 --- a/website/content/api-docs/system/managed-keys.mdx +++ b/website/content/api-docs/system/managed-keys.mdx @@ -87,8 +87,8 @@ $ curl \ a key into the configured backend even if a key is present, if set to false those operations are forbidden if a key exists. -- `allow_store_key` `(string: "false")` - Controls the ability for Vault to generate or import a key within the - configured backend, if "false" those operations will be forbidden. +- `allow_store_key` `(string: "false")` - Controls the ability for Vault to import a key + to the configured backend, if "false" those operations will be forbidden. - `any_mount` `(string: "false")` - Allow usage from any mount point within the namespace if "true". If "false" specific mount points will need their `allowed_managed_keys` parameter to be updated with the key name to