packer

Commit Graph

Author	SHA1	Message	Date
Matthew Hooker	7a189a83a1	fix imports `find . -type f -name '.go' -not -path "./vendor/" -exec goimports -w {} \;`	8 years ago
Matthew Hooker	a831d522be	change run signatures Run now takes a context as well as a statebag. We'll assign the context to the blank identifier to prevent namespace collisions. We'll let the step authors opt-in to using the context. `find . -iname "step_.go" -exec gsed -i'' 's/func \(.\)Run(/func \1Run(_ context.Context, /' {} \;`	8 years ago
Matthew Hooker	366dc3da0a	move multistep imports to helper. gomvpkg -from "github.com/mitchellh/multistep" -to "github.com/hashicorp/packer/helper/multistep"	8 years ago
Matthew Hooker	07b013945f	more consistent flag name	9 years ago
nictrix	6a238a3ef3	add option to skip vnc phase and update docs	9 years ago
James Nugent	c4439aba82	builder/vmware: Add vmx_remove_ethernet_interfaces This commit adds a new option, `vmx_remove_ethernet_interfaces`, to both of the VMWare builders. This is useful when building Vagrant boxes, since Vagrant now produces output such as: ``` WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant when started. Vagrant will stop overwriting this setting in an upcoming release which may pre vent proper networking setup. Below is the detected VMX setting: ethernet0.pcislotnumber = "33" If networking fails to properly configure, it may require this VMX setting. It can be manually applied via the Vagrantfile: Vagrant.configure(2) do \|config\| config.vm.provider :vmware_fusion do \|vmware\| vmware.vmx["ethernet0.pcislotnumber"] = "33" end end ``` This can be avoided entirely by removing the ethernet adapters from the VMX file prior to packaging as a Vagrant box, in which case adapters are created as expected according to the Vagrantfile specification.	9 years ago
Matthew Hooker	9f992b8f80	go files are 0644	9 years ago
Matthew Hooker	81522dced0	move packer to hashicorp	9 years ago
Matthew Hooker	d920b3fbf4	run gofmt	10 years ago
Yuya Kusakabe	699c673536	builder/vmware-esxi: Add step_export If `format` option is configured, packer exports the VM with ovftool. website: Document about OVF Tool and `format` option. post-processor/vsphere: Enable to use `mitchellh.vmware-esx` artifact type and OVF and OVA formats, fixes #1457.	11 years ago
Chris Bednarski	313fcaf0ff	Revert backwards-compatibility break in VMX option casing PR #2309 introduced case-sensitive options in VMX files. This is to support a case-sensitive option called `virtualSSD`. The change made all options case-sensitive, which causes problems with external VMX options provided in user templates. To prevent breakage, this change is being reverted. - Fixes #2574 - Reverts #2542 - Reverts #2309	11 years ago
Marc Siegfriedt	df1be999dc	Fixed case sensitive issue with VMX entries not being overwritten	11 years ago
Mitchell Hashimoto	9bc0dfa389	builder/vmware: disable VNC before packaging	11 years ago
Shawn Neal	5fd9651982	GH 1508 - Ensure Packer VMX is updated and saved We need to ensure the VMWare process has exited before attempting to run VMX file cleanup steps, otherwise VMWare may overwrite our changes. While Packer does its best to ensure VMWare has exited, there's still a race condition on some OSs between VMWare flushing the VMX and Packer updating it. The workaround is to artifically wait 5 seconds. When using the VMX builder its possible for the source machine to have a floppy and/or CD-ROM mounted which gets cloned to the new VM Packer spins up, but have no Packer configuration for those devices. With this change we always attempt to remove the mounted devices regardless of the Packer configuration.	12 years ago
Shawn Neal	7d9c252b3a	Clean VMX step should always remove floppy. When using the VMX builder its possible for the source machine to have a floppy configured which gets cloned to the new VM Packer spins up. When the new VM's Packer config doesn't have a floppy_files config entry, the Packer clean VMX step fails to remove the floppy disk from the new VM. This can cause build failures, for example with the vsphere post processor; generating errors like: * Post-processor failed: Failed: exit status 1 Error: File (/home/teamcity/tmp/buildTmp/packer941120499) could not be found. Opening the cloned VM's VMX file you can clearly see it has a floppy entry from the source machine's VMX file (exact same path) even though the Packer config contains no floppy_files entry.	12 years ago
Mitchell Hashimoto	f01b21c610	builder/vmware: StepCleanVMX	13 years ago

16 Commits (73e8c293ae7987f752a243de315d1f4e8e5f17a4)