Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
P
packer
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Analytics
Analytics
CI / CD
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Kristopher Ruzic
packer
Commits
34164b25
Commit
34164b25
authored
Jun 25, 2014
by
Jack Pearkes
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
post-processor/vagrant-cloud: add docs
parent
6a3c9921
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
103 additions
and
0 deletions
+103
-0
website/source/docs/post-processors/vagrant-cloud.html.markdown
...e/source/docs/post-processors/vagrant-cloud.html.markdown
+102
-0
website/source/layouts/docs.erb
website/source/layouts/docs.erb
+1
-0
No files found.
website/source/docs/post-processors/vagrant-cloud.html.markdown
0 → 100644
View file @
34164b25
---
layout
:
"
docs"
page_title
:
"
Vagrant
Cloud
Post-Processor"
---
# Vagrant Cloud Post-Processor
Type:
`vagrant-cloud`
The Vagrant Cloud post-processor recieves a Vagrant box from the
`vagrant`
post-processor and pushes it to Vagrant Cloud.
[
Vagrant Cloud
](
https://vagrantcloud.com
)
hosts and serves boxes to Vagrant, allowing you to version and distribute
boxes to an organization in a simple way.
You'll need to be familiar with Vagrant Cloud, have an upgraded account
to enable box hosting, and be distributing your box via the
[
shorthand name
](
http://docs.vagrantup.com/v2/cli/box.html
)
configuration.
## Workflow
It's important to understand the workflow that using this post-processor
enforces in order to take full advantage of Vagrant and Vagrant Cloud.
The use of this processor assume that you currently distribute, or plan
to distrubute, boxes via Vagrant Cloud. It also assumes you create Vagrant
Boxes and deliver them to your team in some fashion.
Here is an example workflow:
1.
You use Packer to build a Vagrant Box for the
`virtualbox`
provider
2.
The
`vagrant-cloud`
post-processor is configured to point to the box
`hashicorp/foobar`
on Vagrant Cloud
via the
`box_tag`
configuration
2.
The post-processor receives the box from the
`vagrant`
post-processor
3.
It then creates the configured version, or verifies the existence of it, on Vagrant Cloud
4.
A provider matching the name of the Vagrant provider is then created
5.
The box is uploaded to Vagrant Cloud
6.
The upload is verified
7.
The version is released and available to users of the box
## Configuration
The configuration allows you to specify the target box that you have
access to on Vagrant Cloud, as well as authentication and version information.
### Required:
*
`access_token`
(string) - Your access token for the Vagrant Cloud API.
This can be generated on your
[
tokens page
](
https://vagrantcloud.com/account/tokens
)
.
*
`box_tag`
(string) - The shorthand tag for your box that maps to
Vagrant Cloud, i.e
`hashicorp/precise64`
for
`vagrantcloud.com/hashicorp/precise64`
*
`version`
(string) - The version number, typically incrementing a previous version.
The version string is validated based on
[
Semantic Versioning
](
http://semver.org/
)
. The string must match
a pattern that could be semver, and doesn't validate that the version comes after
your previous versions.
### Optional:
*
`version_description`
(string) - Optionally markdown text used as a full-length
and in-depth description of the version, typically for denoting changes introduced
*
`no_release`
(string) - If set to true, does not release the version
on Vagrant Cloud, making it active. You can manually release the version
via the API or Web UI. Defaults to false.
## Use with Vagrant Post-Processor
You'll need to use the Vagrant post-processor before using this post-processor.
An example configuration is below. Note the use of the array specifying
the execution order.
```
json
{
"variables"
:
{
"version"
:
""
,
"cloud_token"
:
""
},
"builders"
:
[{
...
}],
"post-processors"
:
[
[{
"type"
:
"vagrant"
,
"include"
:
[
"image.iso"
],
"vagrantfile_template"
:
"vagrantfile.tpl"
,
"output"
:
"proxycore_{{.Provider}}.box"
,
},
{
"type"
:
"vagrant-cloud"
,
"box_tag"
:
"hashicorp/precise64"
,
"access_token"
:
"{{user `cloud_token`}}"
,
"version"
:
"{{user `version`}}"
,
"version_description"
:
"- added rabbitmq
\n
- modified db config
\n
- compacted log files"
}]
]
}
```
website/source/layouts/docs.erb
View file @
34164b25
...
...
@@ -61,6 +61,7 @@
<li><a
href=
"/docs/post-processors/docker-import.html"
>
docker-import
</a></li>
<li><a
href=
"/docs/post-processors/docker-push.html"
>
docker-push
</a></li>
<li><a
href=
"/docs/post-processors/vagrant.html"
>
Vagrant
</a></li>
<li><a
href=
"/docs/post-processors/vagrant-cloud.html"
>
Vagrant Cloud
</a></li>
<li><a
href=
"/docs/post-processors/vsphere.html"
>
vSphere
</a></li>
</ul>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment