From 6a62d8c4e899a68bdf0a9fc10b46902f13b2a2a4 Mon Sep 17 00:00:00 2001 From: Yoan Blanc Date: Wed, 6 Oct 2021 22:35:35 +0200 Subject: [PATCH] docs: since Vault 1.0 Unseal is OSS (#12268) * docs: since Vault 1.0 Unseal is OSS Signed-off-by: Yoan Blanc * fixup! docs: since Vault 1.0 Unseal is OSS Signed-off-by: Yoan Blanc * fixup! fixup! docs: since Vault 1.0 Unseal is OSS Signed-off-by: Yoan Blanc --- website/content/api-docs/system/init.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/api-docs/system/init.mdx b/website/content/api-docs/system/init.mdx index 1cd6ce2452..dda291898e 100644 --- a/website/content/api-docs/system/init.mdx +++ b/website/content/api-docs/system/init.mdx @@ -35,7 +35,7 @@ $ curl \ This endpoint initializes a new Vault. The Vault must not have been previously initialized. The recovery options, as well as the stored shares option, are only -available when using Vault HSM. +available when using Auto Unseal. | Method | Path | | :----- | :---------- | @@ -60,7 +60,7 @@ available when using Vault HSM. `secret_shares`. If using Vault HSM with auto-unsealing, this value must be the same as `secret_shares`. -Additionally, the following options are only supported on Vault Pro/Enterprise: +Additionally, the following options are only supported using Auto Unseal: - `stored_shares` `(int: )` – Specifies the number of shares that should be encrypted by the HSM and stored for auto-unsealing. Currently must