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

whitespace and other review changes

Browse source
This commit is contained in:
Tehut 2024-05-01 14:00:23 -07:00
parent b692ba5334
commit 3fb76bf075
2 changed files with 7 additions and 79 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -1,12 +1,15 @@
---
layout: vagrant-cloud
page_title: Migrate to HCP Vagrant Registry
page_title: Migrate to HCP Vagrant Registry
description: "Use Vagrant Cloud's migration tools to move all your artifacts to HashiCorp Cloud Platform (HCP)."
---
# Migrate to HCP Vagrant Registry
# Migrate to HCP Vagrant Registry
~> Note: Vagrant Cloud will be migrated to HCP Vagrant Registry at the end of July 2024.
Your Vagrant Cloud Organization will be put into a read-only state and marked `Migrating` until the migration is complete. During this time boxes will be available in searches and to download, but write functionality like uploading new boxes, releasing versions, and managing settings for your Vagrant Cloud Organization will be unavailable. Your new HCP Registry will not be available until the migration is complete.
When you migrate your default organization your Profile Settings (user name, gravatar url, etc) will no longer be available to manage in Vagrant Cloud and should be managed from your [HCP Settings](https://portal.cloud.hashicorp.com/account-settings).
## Overview
@ -57,7 +60,7 @@ To auto-populate the migration tool with a specific Vagrant Cloud `Organization`
#### 2. Select a Vagrant Cloud organization to migrate
Select a single organization from the dropdown to migrate or select the checkbox `Migrate all organizations` to migrate them all at once to a single HCP Project.
Select a single organization from the dropdown to migrate or select the checkbox `Migrate all organizations` to migrate them all at once to a single HCP Project.
You can select any of the organizations listed in the Vagrant Cloud organization dropdown, even if a specific organization was pre-populated.
@ -85,62 +88,4 @@ It is important to note that while a migrated organization will no longer be ava
## Conclusion
If for some reason you are unable to access your new HCP Registry or your migration does not complete in a timely fashion check our [Troubleshooting Guide ](/vagrant/vagrant-cloud/hcp-vagrant/troubleshooting)or contact us at [support@hashicorp.com](mailto:support@hashicorp.com) with the subject `Vagrant Migration`. Our team will be happy to help you complete your migration or reset your organization state.
If for some reason you are unable to access your new HCP Registry or your migration does not complete successfully, review the [Migration Troubleshooting] (/vagrant/vagrant-cloud/hcp-vagrant/troubleshooting) guide or contact us at [support@hashicorp.com](mailto:support@hashicorp.com) with the subject `HCP Vagrant Migration`. Our team will be happy to help you complete your migration or reset your organization state.

17
website/content/vagrant-cloud/hcp-vagrant/troubleshooting.mdx
View file

@ -18,20 +18,3 @@ In the rare case that an inoperable box was successfully uploaded (e.g legacy bo
If a migration fails, a `retry` icon will appear beside the name of that organization on the [migration status](https://app.beta.vagrantup.com/migration/status) page. Failed migrations can be retried once.
In the event of a second failure, contact us at [support@hashicorp.com](mailto:support@hashicorp.com) with the subject `Vagrant Migration`. Our team will be happy to help you complete your migration or reset your organization state.