upstream/vault
1
0
Fork 0
mirror of https://github.com/hashicorp/vault.git synced 2026-06-11 09:51:16 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 9

Fix replication guide with new paths

Browse source
This commit is contained in:
Jeff Mitchell 2017-08-07 11:52:29 -04:00
parent 36d7719e63
commit ca7e8c96fb
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/source/guides/replication.html.md
View file

@ -24,7 +24,7 @@ the [Vault Replication API documentation](/api/system/replication.html)
To activate the primary, run:
$ vault write -f sys/replication/primary/enable
$ vault write -f sys/replication/performance/primary/enable
There is currently one optional argument: `primary_cluster_addr`. This can be
@ -37,7 +37,7 @@ members of a single cluster and primary/secondary clusters.
To fetch a secondary bootstrap token, run:
$ vault write sys/replication/primary/secondary-token id=<id>
$ vault write sys/replication/performance/primary/secondary-token id=<id>
The value for `id` is opaque to Vault and can be any identifying value you want;
@ -50,7 +50,7 @@ except that the token will be a JWT instead of UUID-formatted random bytes.
To activate a secondary using the fetched token, run:
$ vault write sys/replication/secondary/enable token=<token>
$ vault write sys/replication/performance/secondary/enable token=<token>
You must provide the full token value. Be very careful when running this