ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #14228 from hashicorp/liz/vagrant-cloud-migration-docs 

website: copy vagrant cloud docs
This commit is contained in:
liz abinante! 2017-05-09 11:34:24 -07:00 committed by GitHub
parent 8f810cdee0 de3e6ad416
commit 35fc047b69
3 changed files with 29 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/enterprise/faq/index.html.md
View File

@ -11,3 +11,5 @@ description: |-
[Monolithic Artifacts](/docs/enterprise/faq/monolithic-artifacts.html) - *How do I build multiple applications into one artifact?* [Monolithic Artifacts](/docs/enterprise/faq/monolithic-artifacts.html) - *How do I build multiple applications into one artifact?*
[Rolling Deployments](/docs/enterprise/faq/rolling-deployments.html) - *How do I configure rolling deployments?* [Rolling Deployments](/docs/enterprise/faq/rolling-deployments.html) - *How do I configure rolling deployments?*
[Vagrant Cloud Migration](/docs/enterprise/faq/vagrant-cloud-migration.html) - *How can I prepare for the Vagrant Cloud Mirgration?*

23
website/source/docs/enterprise/faq/vagrant-cloud-migration.html.md Normal file
View File

@ -0,0 +1,23 @@
---
layout: "enterprise"
page_title: "Vagrant Cloud Migration - FAQ - Terraform Enterprise"
sidebar_current: "docs-enterprise-faq-vagrant-cloud-migration"
description: |-
Vagrant-related functionality will be moved from Terraform Enterprise into its own product, Vagrant Cloud. This migration is currently planned for June 27th, 2017.
---
# Vagrant Cloud Migration
Vagrant-related functionality will be moved from Terraform Enterprise into its own product, Vagrant Cloud. This migration is currently planned for **June 27th, 2017**.
All existing Vagrant boxes will be moved to the new system on that date. All users, organizations, and teams will be copied as well.
## Authentication Tokens
No existing Terraform Enterprise authentication tokens will be transferred. To prevent a disruption of service for Vagrant-related operations, users must create a new authentication token and check "Migrate to Vagrant Cloud" and begin using these tokens for creating and modifying Vagrant boxes. These tokens will be moved on the migration date.
Creating a token via `vagrant login` will also mark a token as "Migrate to Vagrant Cloud".
## More Information
At least 1 month prior to the migration, we will be releasing more information on the specifics and impact of the migration.

4
website/source/layouts/enterprise.erb
View File

@ -176,6 +176,10 @@
<li<%= sidebar_current("docs-enterprise-faq-deployments") %>> <li<%= sidebar_current("docs-enterprise-faq-deployments") %>>
<a href="/docs/enterprise/faq/rolling-deployments.html">Rolling Deployments</a> <a href="/docs/enterprise/faq/rolling-deployments.html">Rolling Deployments</a>
</li> </li>
<li<%= sidebar_current("docs-enterprise-faq-vagrant-cloud-migration") %>>
<a href="/docs/enterprise/faq/vagrant-cloud-migration.html">Vagrant Cloud Migration</a>
</li>
</ul> </ul>
</li> </li>