From ad36c8c59448a5464f65b4742f05238622d291e1 Mon Sep 17 00:00:00 2001 From: temp Date: Tue, 4 Oct 2022 14:16:31 -0400 Subject: [PATCH 1/2] no-op commit due to failed cherry-picking From 31ebe1956dd1f14b3844dcc139c62d7120f05afd Mon Sep 17 00:00:00 2001 From: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> Date: Tue, 4 Oct 2022 13:16:14 -0500 Subject: [PATCH 2/2] Merge pull request #14870 from hashicorp/docs/hyperlink-fixes docs: Windows tutorial hyperlink fix #2 --- website/content/docs/connect/proxies/envoy.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/connect/proxies/envoy.mdx b/website/content/docs/connect/proxies/envoy.mdx index 808cd80e6c72..6ff35a0ff710 100644 --- a/website/content/docs/connect/proxies/envoy.mdx +++ b/website/content/docs/connect/proxies/envoy.mdx @@ -176,7 +176,7 @@ The [Advanced Configuration](#advanced-configuration) section describes addition ### Bootstrap Envoy on Windows VMs -> Complete the [Connect Services on Windows Workloads to Consul Service Mesh tutorial](https://learn.hashicorp.com/tutorials/consul/developer-mesh/consul-windows-workloads?utm_source=docs) to learn how to deploy Consul and use its service mesh on Windows VMs. +> Complete the [Connect Services on Windows Workloads to Consul Service Mesh tutorial](https://learn.hashicorp.com/tutorials/consul/consul-windows-workloads?utm_source=docs) to learn how to deploy Consul and use its service mesh on Windows VMs. If you are running Consul on a Windows VM, attempting to bootstrap Envoy with the `consul connect envoy` command returns the following output: