-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Conversation
Includes information related to post migration including Vagrant Cloud behavior and API usage.
There was a problem hiding this 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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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: |
76b9d94
to
eb078bd
Compare
Add post migration information
Includes information related to post migration including Vagrant Cloud
behavior and API usage.