haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

website: Packer box version should be variable 

When using multiple builders, the post-processor could yield different results for the `{{timestamp}}` interpolation.

By using a variable instead, the version will be consistent across all builders.

https://github.com/hashicorp/packer/issues/4973
This commit is contained in:
Justin Campbell 2017-06-13 17:09:40 -04:00
parent f3535e393e
commit 17691bac10
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
website/source/docs/vagrant-cloud/vagrant-cloud-migration.html.md
View File

@ -65,7 +65,8 @@ For example, if your Packer post-processor JSON looks like this:
```json
{
"variables": {
"atlas_token": "{{env `ATLAS_TOKEN`}}"
"atlas_token": "{{env `ATLAS_TOKEN`}}",
"version": "1.0.{{timestamp}}"
},
"builders": [
],
@ -76,7 +77,7 @@ For example, if your Packer post-processor JSON looks like this:
"artifact": "hashicorp/example",
"artifact_type": "vagrant.box",
"metadata": {
"version": "1.0.{{timestamp}}"
"version": "{{user `version`}}"
}
}
]
@ -88,7 +89,8 @@ You must replace the `atlas` post-processor with the `vagrant` and `vagrant-clou
```json
{
"variables": {
"vagrantcloud_token": "{{env `VAGRANTCLOUD_TOKEN`}}"
"vagrantcloud_token": "{{env `VAGRANTCLOUD_TOKEN`}}",
"version": "1.0.{{timestamp}}"
},
"builders": [
],
@ -102,7 +104,7 @@ You must replace the `atlas` post-processor with the `vagrant` and `vagrant-clou
"type": "vagrant-cloud",
"access_token": "{{user `vagrantcloud_token`}}",
"box_tag": "hashicorp/example",
"version": "1.0.{{timestamp}}"
"version": "{{user `version`}}"
}
]
]