From 3c4f1f72bc544b2379ad309fd7104fc14f56b257 Mon Sep 17 00:00:00 2001 From: "Chris S. Kim" Date: Tue, 27 Jun 2023 11:07:44 -0400 Subject: [PATCH] PR feedback --- website/content/docs/connect/ca/vault.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/connect/ca/vault.mdx b/website/content/docs/connect/ca/vault.mdx index e02c2480101e2..828a6937cae18 100644 --- a/website/content/docs/connect/ca/vault.mdx +++ b/website/content/docs/connect/ca/vault.mdx @@ -139,10 +139,10 @@ The key after the slash refers to the corresponding option name in the agent con path does not exist, Consul will attempt to mount and configure this automatically. - When WAN Federation is enabled, every secondary datacenter which shares a common Vault cluster - must specify a unique `intermediate_pki_path`. If a Vault cluster is not being used by more than - one Consul datacenter, then this is not required. However, it is still recommended to use a - unique `intermediate_pki_path` per datacenter for operational and diagnostic clarity. + When WAN federation is enabled, every secondary datacenter that shares a common Vault cluster + must specify a unique `intermediate_pki_path`. If a Vault cluster is not used by more than one Consul datacenter, + then you do not need to specify a unique value for the `intermediate_pki_path`. We still recommend using a + unique `intermediate_pki_path` for each datacenter, however, to improve operational and diagnostic clarity. - `IntermediatePKINamespace` / `intermediate_pki_namespace` (`string: `) - The absolute namespace that the `IntermediatePKIPath` is in. Setting this parameter overrides the `Namespace` option for the `IntermediatePKIPath`. Introduced in 1.12.3.