Vagrant Cloud Migration Announcement

We are excited to announce that HashiCorp Vagrant features will be extracted from Atlas on June 27th into its own product, HashiCorp Vagrant Cloud.

Features include:

• Vagrant Box Creation to publish public or private Vagrant boxes for others to consume
• Vagrant Box Versioning to update boxes and communicate these changes to consumers
• Vagrant Box Catalog to search and discover public Vagrant boxes

Going forward, Vagrant Cloud will be developed independently, which allows us to improve current functionality and eventually provide new services around Vagrant.

If you only use Vagrant to download and run public boxes, then nothing is changing. All box names, versions, and URLs will stay the same (or redirect) with no changes to your workflow or Vagrantfiles.

Read more to learn about the migration of existing hosted Vagrant boxes and accounts.

Background

Vagrant Cloud was HashiCorp’s first hosted product, providing Vagrant box discovery, management, and sharing for our first open-source product, Vagrant. It eventually evolved to be known as Atlas and then Terraform Enterprise, which is now focusing solely on Terraform and Packer features.

Atlas has been split from a unified platform into HashiCorp’s suite of products — Terraform Enterprise, Consul Enterprise, Vault Enterprise, Vagrant Cloud, and eventually Nomad Enterprise. All of the Atlas functionality exists, just split over these products. Today, only Terraform Enterprise and Vagrant Cloud functionality exists at the atlas.hashicorp.com domain, and it will be moved over to a Terraform Enterprise specific domain in the near future. Once that is complete, the Atlas brand name will be removed.

Vagrant Boxes, Users, Organizations, and Teams

All Vagrant boxes will be moved to the new Vagrant Cloud on June 27th. Additionally, all users and organizations will be copied. Any existing box collaborations or team ACLs will persist into the new system.

All existing box names (hashicorp/precise64) and URLs will continue working as-is, or permanently redirect to the correct location. If you’re only using public Vagrant boxes, no changes will be required to your Vagrantfiles or workflow. Users of private Vagrant boxes will need to create a new authentication (see below), and activate their Vagrant Cloud account after the migration has completed.

Vagrant Cloud users and organizations will be considered inactive in the future if they have not logged into Vagrant Cloud after the migration and do not have any published Vagrant boxes. Inactive user accounts will be deleted on or after October 1st, 2017.

Vagrant Cloud Account Activation

In order to begin using Vagrant Cloud with your Atlas account, you will first need to activate your Vagrant Cloud account. This will require you to login to Atlas, as well as confirm your password (and 2FA credentials, if configured). There will be links and instructions on the Vagrant Cloud login screen directing you to do this.

During Vagrant Cloud account activation, you will create a new password for Vagrant Cloud and optionally configure 2FA. Your pre-existing Atlas account, password, and 2FA configuration will remain unchanged within Atlas.

New users of Vagrant Cloud can always create a new account for free, at any time.

Authentication Tokens

If you are currently using an authentication token to interact with Atlas for Vagrant features, you will need to generate a new Vagrant Cloud token prior to June 27th. You can see your existing tokens and generate new tokens on the Tokens page of your account settings.

When creating this new token, select Migrate to Vagrant Cloud.

You can see which authentication tokens which will be copied to Vagrant Cloud in the token list.

Only these authentication tokens will be moved to Vagrant Cloud on June 27th. They will also be removed from Terraform Enterprise at this time, and will no longer work for Terraform or Packer operations. If you do not create a token in Atlas by June 27th, you will need to create a token within Vagrant Cloud after the migration.

Packer and Terraform Enterprise

Packer has two post-processors which can create Vagrant boxes in Terraform Enterprise (Atlas): atlas and vagrant-cloud. The atlas post-processor will no longer create Vagrant boxes after June 27th. If you are currently publishing Vagrant boxes with Packer, please ensure that you are using the vagrant-cloud post-processor. For examples, please see the Vagrant Cloud Migration docs on vagrantup.com.

Vagrant Share

Vagrant Share via Atlas has been deprecated, and instead Vagrant supports native integration with ngrok. Users of Vagrant Share should switch to the ngrok-powered Vagrant Share driver prior to June 27th, which will become the default in the next version of Vagrant.

Downtime

There will be a brief outage of Vagrant services within Atlas/Terraform Enterprise on June 27th at 6PM EDT/3PM PDT (click here for conversion into other time zones) until the migration is complete. We estimate that this will take less than 30 minutes. Please visit status.hashicorp.com for up-to-date information about the migration status.

More Information

For more detailed information about the upcoming migration, please visit the Vagrant Cloud docs on vagrantup.com. If you have any questions about Vagrant Cloud or the migration, please email support@hashicorp.com.