From 76f22fac24a30c862f61f93fa1ca809ed2b21d0d Mon Sep 17 00:00:00 2001 From: Altabay-HashiCorp <163007238+Altabay-HashiCorp@users.noreply.github.com> Date: Thu, 31 Oct 2024 14:49:26 +0100 Subject: [PATCH] fix url typo in removing seal ha (#28818) --- website/content/docs/configuration/seal/seal-ha.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/configuration/seal/seal-ha.mdx b/website/content/docs/configuration/seal/seal-ha.mdx index 0c3c4dc9ef72..9b860b404852 100644 --- a/website/content/docs/configuration/seal/seal-ha.mdx +++ b/website/content/docs/configuration/seal/seal-ha.mdx @@ -156,6 +156,6 @@ Migrating back to a single seal may result in data loss if an operator does not use the HA seal feature. To migrate back to a single seal: 1. Perform a [seal migration](/vault/docs/concepts/seal#seal-migration) as described. -2. Monitor [`sys/sealwrap/rewrap`](/vault/docs/api-docs/system/sealwrap-rewrap) until the API returns `fully_wrapped=true`. +2. Monitor [`sys/sealwrap/rewrap`](/vault/api-docs/system/sealwrap-rewrap) until the API returns `fully_wrapped=true`. 3. Remove `enable_multiseal` from all Vault configuration files in the cluster. 4. Restart Vault. \ No newline at end of file