upstream/vagrant
1
0
Fork 0
mirror of https://github.com/hashicorp/vagrant.git synced 2026-05-28 04:36:05 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Fixup copy and add link within nav

Browse source
This commit is contained in:
Chris Roberts 2024-05-03 14:59:10 -07:00
parent 106b51b253
commit eb078bd7ac
2 changed files with 9 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
website/content/vagrant-cloud/hcp-vagrant/post-migration-guide.mdx
View file

@ -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:
<VAGRANT_CLOUD_TOKEN>;<HCP_TOKEN>
```
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:
```
;<HCP_TOKEN>
@ -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:

4
website/data/vagrant-cloud-nav-data.json
View file

@ -9,6 +9,10 @@
{
"title": "Migration Troubleshooting",
"path": "hcp-vagrant/troubleshooting"
},
{
"title": "Post Migration",
"path": "hcp-vagrant/post-migration-guide"
}
]
},