From eb078bd7ac289a4f7be29d98cd5d40e7240c3159 Mon Sep 17 00:00:00 2001 From: Chris Roberts Date: Fri, 3 May 2024 14:59:10 -0700 Subject: [PATCH] Fixup copy and add link within nav --- .../vagrant-cloud/hcp-vagrant/post-migration-guide.mdx | 10 +++++----- website/data/vagrant-cloud-nav-data.json | 4 ++++ 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx b/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx index 9c3d8fa30..6c3415b17 100644 --- a/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx +++ b/website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx @@ -6,11 +6,11 @@ description: "Learn about how Vagrant and Vagrant Cloud will behave after migrat # Migrating to HCP Vagrant Registry -This document describes the behavior of Vagrant Cloud after an organization is migrated to HCP Vagrant Registry. For information on migrating to HCP Vagrant Registry please see the [migration guide](/vagrant-cloud/hcp-vagrant/migration-guide). +This document describes the behavior of Vagrant Cloud after an organization is migrated to HCP Vagrant Registry. For information on migrating to HCP Vagrant Registry please see the [migration guide](/vagrant/vagrant-cloud/hcp-vagrant/migration-guide). # Vagrant Cloud Redirects -After an ogranization has been migrated to HCP Vagrant Registry any requests Vagrant Cloud receives for that organization, or any boxes within that organization, will be automatically redirected to the proper location on HCP Vagrant Registry. +After an organization has been migrated to HCP Vagrant Registry any requests Vagrant Cloud receives for that organization, or any boxes within that organization, will be automatically redirected to the proper location on HCP Vagrant Registry. # API @@ -26,7 +26,7 @@ The format of the composite access token is: ; ``` -If all organizations have been migrated to HCP Vagrant Registry the Vagrant Cloud access token will not be needed and the format of the access token is: +If all organizations have been migrated to HCP Vagrant Registry the Vagrant Cloud access token will not be needed. The format of the access token is: ``` ; @@ -36,8 +36,8 @@ If all organizations have been migrated to HCP Vagrant Registry the Vagrant Clou The following prerequisites are required for generating an HCP access token: -* [HCP Service Principal](https://developer.hashicorp.com/hcp/docs/hcp/admin/iam/service-principals) -* [HCP CLI](https://developer.hashicorp.com/hcp/docs/cli) +* [HCP Service Principal](/hcp/docs/hcp/admin/iam/service-principals) +* [HCP CLI](/hcp/docs/cli) Using the `CLIENT_ID` and `CLIENT_SECRET` from the HCP service principal login to HCP using the `hcp` command: diff --git a/website/data/vagrant-cloud-nav-data.json b/website/data/vagrant-cloud-nav-data.json index 155e05a1d..951a33923 100644 --- a/website/data/vagrant-cloud-nav-data.json +++ b/website/data/vagrant-cloud-nav-data.json @@ -9,6 +9,10 @@ { "title": "Migration Troubleshooting", "path": "hcp-vagrant/troubleshooting" + }, + { + "title": "Post Migration", + "path": "hcp-vagrant/post-migration-guide" } ] },