From cf4af7c765b1ce3fc605902b659acb3e452ca321 Mon Sep 17 00:00:00 2001 From: Luke Kysow <1034429+lkysow@users.noreply.github.com> Date: Mon, 25 Jul 2022 09:30:37 -0700 Subject: [PATCH] Re-document peering disabled (#13879) Change wording because it does have effect on clients because it disables peering in the UI served from that client. --- website/content/docs/agent/config/config-files.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/agent/config/config-files.mdx b/website/content/docs/agent/config/config-files.mdx index 6b902987ee..c886775084 100644 --- a/website/content/docs/agent/config/config-files.mdx +++ b/website/content/docs/agent/config/config-files.mdx @@ -556,9 +556,9 @@ Valid time units are 'ns', 'us' (or 'µs'), 'ms', 's', 'm', 'h'." The following sub-keys are available: - `enabled` ((#peering_enabled)) (Defaults to `true`) Controls whether cluster peering is enabled. - Has no effect on Consul clients, only on Consul servers. When disabled, all peering APIs will return + When disabled, the UI won't show peering, all peering APIs will return an error, any peerings stored in Consul already will be ignored (but they will not be deleted), - all peering connections from other clusters will be rejected. This was added in Consul 1.13.0. + and all peering connections from other clusters will be rejected. This was added in Consul 1.13.0. - `partition` - This flag is used to set the name of the admin partition the agent belongs to. An agent can only join