iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update incorrect documentation on vagrant builder. 

The packer option `vagrantfile_template` is not used.
This change corrects the documentation with the correct option name.

Closes #7414
This commit is contained in:
Esten Rye 2019-03-15 20:22:51 -05:00
parent 8853fc1946
commit 8f10683a20
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/builders/vagrant.html.md
View File

@ -74,7 +74,7 @@ one, by using `global_id` instead of `source_box`.
not recommended since OVA files can be very large and corruption does happen not recommended since OVA files can be very large and corruption does happen
from time to time. from time to time.
- `vagrantfile_template` (string) - a path to a golang template for a - `template` (string) - a path to a golang template for a
vagrantfile. Our default template can be found vagrantfile. Our default template can be found
[here](https://github.com/hashicorp/packer/blob/a6d1d852bb0643e3593cc5d3dfe5ed80c4409b65/builder/vagrant/step_create_vagrantfile.go#L23-L30). So far the only template variables available to you are {{ .BoxName }} and [here](https://github.com/hashicorp/packer/blob/a6d1d852bb0643e3593cc5d3dfe5ed80c4409b65/builder/vagrant/step_create_vagrantfile.go#L23-L30). So far the only template variables available to you are {{ .BoxName }} and
{{ .SyncedFolder }}, which correspond to the Packer options `box_name` and {{ .SyncedFolder }}, which correspond to the Packer options `box_name` and