From cc222872bcfdcbcfc9a9e5984cb4ef1d1b9435ee Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Tomas=20B=C3=A4ckman?=
 <50198527+tomasbackman@users.noreply.github.com>
Date: Mon, 8 Jun 2020 15:26:49 +0200
Subject: [PATCH] Add note about flag -target=recovery for auto-unseal mode
 (#9163)

---
 website/pages/guides/operations/rekeying-and-rotating.mdx | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/website/pages/guides/operations/rekeying-and-rotating.mdx b/website/pages/guides/operations/rekeying-and-rotating.mdx
index 425f50a32f..d835e56abd 100644
--- a/website/pages/guides/operations/rekeying-and-rotating.mdx
+++ b/website/pages/guides/operations/rekeying-and-rotating.mdx
@@ -67,6 +67,8 @@ Rekeying the Vault requires a quorum of unseal keys. Before continuing, you
 should ensure enough unseal key holders are available to assist with the
 rekeying to match the threshold configured when the keys were issued.
 
+Please also observe that if Vault is configured with *auto_unseal* (and the keys thus are the *recovery_keys*), an extra flag `-target=recovery` has to be provided for each of the commands below. Otherwise the *key-shares* will default to **1** no matter what value you set.
+
 First, initialize a rekeying operation. The flags represent the **newly
 desired** number of keys and threshold: