From 0d8bad1d020a0f02eccc83b1e2bea0e5782716a7 Mon Sep 17 00:00:00 2001 From: trujillo-adam Date: Fri, 21 Oct 2022 13:32:47 -0700 Subject: [PATCH] tweaks to the description in the configuration reference --- .../content/docs/api-gateway/configuration/meshservice.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/website/content/docs/api-gateway/configuration/meshservice.mdx b/website/content/docs/api-gateway/configuration/meshservice.mdx index dcb1e6f9f8..8847495874 100644 --- a/website/content/docs/api-gateway/configuration/meshservice.mdx +++ b/website/content/docs/api-gateway/configuration/meshservice.mdx @@ -34,9 +34,9 @@ Specifies the name of the service in the Consul service mesh to send traffic to. * Required: required ### peer -Specifies the name of the Consul peer exporting the service. If not specified, the service is assumed to be in the local datacenter. +Specifies the name of the peered Consul cluster from where the service is exported. If not specified, Consul defaults to the local datacenter. -Note that a [ServiceResolver](/docs/connect/config-entries/service-resolver) is also required for the referenced Consul service indicating what peer the service is exported by. +You must apply a [`ServiceResolver`](/docs/connect/config-entries/service-resolver) for the referenced service. The `ServiceResolver` configuration entry enables Consul to resolve routes to upstream service instances. * Type: string * Required: optional