From ca7e8c96fb725387f8ba7ff4e603bcf78bb21c02 Mon Sep 17 00:00:00 2001 From: Jeff Mitchell Date: Mon, 7 Aug 2017 11:52:29 -0400 Subject: [PATCH] Fix replication guide with new paths --- website/source/guides/replication.html.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/website/source/guides/replication.html.md b/website/source/guides/replication.html.md index b717c8203a..8e093bfffd 100644 --- a/website/source/guides/replication.html.md +++ b/website/source/guides/replication.html.md @@ -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= + $ vault write sys/replication/performance/primary/secondary-token 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= + $ vault write sys/replication/performance/secondary/enable token= You must provide the full token value. Be very careful when running this