luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

fix typo in vault operator init cmd (#11792)

This commit is contained in:
Shanker Naik 2021-06-10 20:09:53 +05:30 committed by GitHub
parent 3e8a4bad1a
commit 35593978ed
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
command/operator_init.go
View File

@ -448,7 +448,7 @@ func (c *OperatorInitCommand) init(client *api.Client, req *api.InitRequest) int
c.UI.Output("") c.UI.Output("")
c.UI.Output(wrapAtLength(fmt.Sprintf( c.UI.Output(wrapAtLength(fmt.Sprintf(
"Vault does not store the generated master key. Without at least %d "+ "Vault does not store the generated master key. Without at least %d "+
"key to reconstruct the master key, Vault will remain permanently "+ "keys to reconstruct the master key, Vault will remain permanently "+
"sealed!", "sealed!",
req.SecretThreshold))) req.SecretThreshold)))

2
website/content/intro/getting-started/deploy.mdx
View File

@ -128,7 +128,7 @@ distribute the key shares printed above. When the Vault is re-sealed,
restarted, or stopped, you must supply at least 3 of these keys to unseal it restarted, or stopped, you must supply at least 3 of these keys to unseal it
before it can start servicing requests. before it can start servicing requests.
Vault does not store the generated master key. Without at least 3 key to Vault does not store the generated master key. Without at least 3 keys to
reconstruct the master key, Vault will remain permanently sealed! reconstruct the master key, Vault will remain permanently sealed!
It is possible to generate new unseal keys, provided you have a quorum of It is possible to generate new unseal keys, provided you have a quorum of