From e554c3d8f7b9a2908ca40c63219435f294b17173 Mon Sep 17 00:00:00 2001 From: Justin Campbell Date: Tue, 23 May 2017 11:15:24 -0400 Subject: [PATCH 1/3] website: Un-deprecate vagrant-cloud post-processor --- website/source/docs/post-processors/vagrant-cloud.html.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/website/source/docs/post-processors/vagrant-cloud.html.md b/website/source/docs/post-processors/vagrant-cloud.html.md index e070ffc88..b8fb8f8eb 100644 --- a/website/source/docs/post-processors/vagrant-cloud.html.md +++ b/website/source/docs/post-processors/vagrant-cloud.html.md @@ -11,10 +11,6 @@ description: |- # Vagrant Cloud Post-Processor -~> Vagrant Cloud has been superseded by Atlas. Please use the [Atlas -post-processor](/docs/post-processors/atlas.html) instead. Learn more about -[Atlas](https://atlas.hashicorp.com/). - Type: `vagrant-cloud` The Packer Vagrant Cloud post-processor receives a Vagrant box from the From e934633df9ce09b5126ef93eb8c75c6f8d9141a8 Mon Sep 17 00:00:00 2001 From: Justin Campbell Date: Tue, 23 May 2017 11:16:50 -0400 Subject: [PATCH 2/3] website: Remove Vagrant from Atlas post-processor --- website/source/docs/post-processors/atlas.html.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/website/source/docs/post-processors/atlas.html.md b/website/source/docs/post-processors/atlas.html.md index a8d1e9451..91ea62540 100644 --- a/website/source/docs/post-processors/atlas.html.md +++ b/website/source/docs/post-processors/atlas.html.md @@ -14,7 +14,7 @@ Type: `atlas` The Atlas post-processor uploads artifacts from your packer builds to Atlas for hosting. Artifacts hosted in Atlas are automatically made available for use -with Vagrant and Terraform, and Atlas provides additional features for managing +with Terraform, and Atlas provides additional features for managing versions and releases. [Learn more about packer in Atlas.](https://atlas.hashicorp.com/help/packer/features) @@ -58,8 +58,7 @@ The configuration allows you to specify and access the artifact in Atlas. `cloudstack.image`, `digitalocean.image`, `docker.image`, `googlecompute.image`, `hyperv.image`, `oneandone.image`, `openstack.image`, `parallels.image`, `profitbricks.image`, `qemu.image`, - `triton.image`, `virtualbox.image`, `vmware.image`, `custom.image`, and - `vagrant.box`. + `triton.image`, `virtualbox.image`, `vmware.image`, and `custom.image`. ### Optional: @@ -74,9 +73,7 @@ you can also use `token` configuration option. you're using Atlas Enterprise in your own network. Defaults to `https://atlas.hashicorp.com/api/v1`. -- `metadata` (map) - Send metadata about the artifact. If the artifact type - is `vagrant.box`, you must specify a `provider` metadata about what - provider to use. +- `metadata` (map) - Send metadata about the artifact. - `description` (string) - Inside the metadata blob you can add a information about the uploaded artifact to Atlas. This will be reflected in the box From db91f94a0846dea32efc20833359208570d704bf Mon Sep 17 00:00:00 2001 From: Justin Campbell Date: Tue, 23 May 2017 11:21:34 -0400 Subject: [PATCH 3/3] website: Add Vagrant note to atlas post-processor --- website/source/docs/post-processors/atlas.html.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/website/source/docs/post-processors/atlas.html.md b/website/source/docs/post-processors/atlas.html.md index 91ea62540..52df8a836 100644 --- a/website/source/docs/post-processors/atlas.html.md +++ b/website/source/docs/post-processors/atlas.html.md @@ -22,6 +22,8 @@ You can also use the push command to [run packer builds in Atlas](/docs/commands/push.html). The push command and Atlas post-processor can be used together or independently. +~> If you'd like to publish a Vagrant box to [Vagrant Cloud](https://vagrantcloud.com), you must use the [`vagrant-cloud`](/docs/post-processors/vagrant-cloud.html) post-processor. + ## Workflow To take full advantage of Packer and Atlas, it's important to understand the