Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add post migration information #13387

Merged
merged 2 commits into from
May 3, 2024
Merged

Add post migration information #13387

merged 2 commits into from
May 3, 2024

Conversation

chrisroberts
Copy link
Member

Includes information related to post migration including Vagrant Cloud
behavior and API usage.

Includes information related to post migration including Vagrant Cloud
behavior and API usage.
allisonlarson
allisonlarson previously approved these changes May 3, 2024
Copy link
Contributor

@allisonlarson allisonlarson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The content looks good to me! I added a spelling correction & one suggestion for clairy, but copy is by no means my expertise so it's not blocking


# 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.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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.

<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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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:

@chrisroberts chrisroberts merged commit faf9014 into main May 3, 2024
12 checks passed
@chrisroberts chrisroberts deleted the post-migration-info branch May 3, 2024 22:16
chrisroberts added a commit that referenced this pull request May 3, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants