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

Merge pull request #7044 from hashicorp/fix_7026 

make displayname docs very clear about inheritance
This commit is contained in:
Adrien Delorme 2018-11-27 11:57:06 +01:00 committed by GitHub
parent 198b6ad0cc d0afc905fc
commit c6cf3b6bb1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/source/docs/builders/vmware-vmx.html.md.erb
View File

@ -82,7 +82,9 @@ builder.
value in your vmx file. It will also override the "displayname" if you have value in your vmx file. It will also override the "displayname" if you have
set it in the "vmx_data" Packer option. This option is useful if you are set it in the "vmx_data" Packer option. This option is useful if you are
chaining vmx builds and want to make sure that the display name of each step chaining vmx builds and want to make sure that the display name of each step
in the chain is unique. in the chain is unique: the vmware-vmx builder will use the displayname of
the VM being cloned from if it is not explicitly specified via the vmx_data
section or the displayname property.
- `floppy_dirs` (array of strings) - A list of directories to place onto - `floppy_dirs` (array of strings) - A list of directories to place onto
the floppy disk recursively. This is similar to the `floppy_files` option the floppy disk recursively. This is similar to the `floppy_files` option