From 0ff4be119e5af898209c5ce1559045318a3fc3ab Mon Sep 17 00:00:00 2001 From: Robin Beck Date: Thu, 23 Jun 2022 12:06:39 -0600 Subject: [PATCH] updates learn links (#2230) --- website/content/docs/concepts/service-discovery.mdx | 6 +++--- website/content/docs/getting-started/index.mdx | 2 +- website/data/docs-nav-data.json | 4 ++-- 3 files changed, 6 insertions(+), 6 deletions(-) diff --git a/website/content/docs/concepts/service-discovery.mdx b/website/content/docs/concepts/service-discovery.mdx index ace6b950c..cee1c8e48 100644 --- a/website/content/docs/concepts/service-discovery.mdx +++ b/website/content/docs/concepts/service-discovery.mdx @@ -21,13 +21,13 @@ as hosts. Boundary supports target/service discovery in three primary workflows: -**[Manual configuration](https://learn.hashicorp.com/tutorials/boundary/manage-targets?in=boundary/basic-administration)**: +**[Manual configuration](https://learn.hashicorp.com/tutorials/boundary/oss-manage-targets)**: Boundary administrators can manually configure static hosts and targets via the administrator UI and CLI. Manual configuration of targets with static hosts requires knowledge of the IP address or endpoint used to connect to a host. -**[Service discovery via configuration as code with Terraform](https://learn.hashicorp.com/tutorials/boundary/getting-started-config)**: +**[Service discovery via configuration as code with Terraform](https://learn.hashicorp.com/tutorials/boundary/oss-getting-started-config)**: Boundary is fully programmatically instrumented and the discovery and configuration of new infrastructure targets can be automated with [Boundary’s Terraform provider](https://registry.terraform.io/providers/hashicorp/boundary/latest/docs). @@ -56,4 +56,4 @@ external resources should be ingested into the catalog by Currently, Boundary supports dynamic host catalog implementations for AWS and Azure and we will continue to grow this ecosystem to support additional providers. -You can get started with dynamic host catalogs [here](https://learn.hashicorp.com/tutorials/boundary/azure-host-catalogs?in=boundary/configuration). \ No newline at end of file +You can get started with dynamic host catalogs [here](https://learn.hashicorp.com/tutorials/boundary/azure-host-catalogs). \ No newline at end of file diff --git a/website/content/docs/getting-started/index.mdx b/website/content/docs/getting-started/index.mdx index abf73f018..f2fa3368e 100644 --- a/website/content/docs/getting-started/index.mdx +++ b/website/content/docs/getting-started/index.mdx @@ -16,6 +16,6 @@ To get started with HCP Boundary, users need: - A [HashiCorp Cloud Platform](https://portal.cloud.hashicorp.com/sign-up) account - A [Boundary binary](https://www.boundaryproject.io/downloads) in your `$PATH` -- Optionally, an [installation of Boundary Desktop](https://learn.hashicorp.com/tutorials/boundary/getting-started-desktop-app) +- Optionally, an [installation of Boundary Desktop](https://learn.hashicorp.com/tutorials/boundary/hcp-getting-started-desktop-app) If you prefer to Get Started on your local machine, refer to [Run and Login in Dev Mode](/docs/oss/installing/run-and-login). For more information on Boundary OSS and self-managed installations, refer to [Boundary OSS](/docs/oss/index). \ No newline at end of file diff --git a/website/data/docs-nav-data.json b/website/data/docs-nav-data.json index 636a85c42..b37320118 100644 --- a/website/data/docs-nav-data.json +++ b/website/data/docs-nav-data.json @@ -294,7 +294,7 @@ }, { "title": "Common Workflows", - "href": "https://learn.hashicorp.com/collections/boundary/basic-administration" + "href": "https://learn.hashicorp.com/boundary" }, { "title": "Common Workflows", @@ -356,7 +356,7 @@ }, { "title": "Desktop", - "href": "https://learn.hashicorp.com/tutorials/boundary/getting-started-desktop-app" + "href": "https://learn.hashicorp.com/tutorials/boundary/hcp-getting-started-desktop-app" } ] },