adding explanation for allow_store_key flag , based on internal engineering conversation. (#17258)

This commit is contained in:
ssurana90 2023-08-18 01:00:38 +02:00 committed by GitHub
parent c6f2845f6b
commit 4ff9fb3fd3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -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 import a key
to the configured backend, if "false" those operations will be forbidden.
- `allow_store_key` `(string: "false")` - Controls the ability for Vault to export a Vault private key
to the configured HSM, 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