- Import errors were not very useful messages, obtain the import status
from the import task as AWS reports it
- Interpolate s3_key_name as per PR comments (rather than hard-code the
generated parts of the default value)
- Remove descriptions on AWS import job, they are optional anyway.
- s3_key_name is now optional, default is equivilent to
"packer-import-{{timestamp}}"
- Remove restriction on builder used, anything producing an OVA is okay
- Fix task and ova description passed to import API call, correctly
adds timestamp to both
- Documentation updated
- Remove VMware-specific text
- Mark s3_key_name as optional
- Remove s3_key_name from example now it's optional
- Explain the import process more clearly in example
- Tags follows the same approach as the amazon-ebs builder
- Clean up some debug messages
- Improve readability by pulling out AMI id into seperate variable
Note: this duplicates the tag creation code in
builder/amazon/common/step_create_tags.go. Maybe this should be a multistep
post-processor instead, and we re-use steps from the builder.
- Add example of usage
- Expand on how it works
- Correctly reflect the hard requirement for AWS access keys and region
- Add tag support documentation
- S3 object uploaded removed after import (with disable option)
- Indicate to user when import is complete
- Close the source file uploaded after upload is done
- Each step of import process logs a debug message
Like the 'puppet-masterless' and 'puppet-server' provisioners (and
unlike the 'chef-solo' and 'chef-client' provisioners), the
'ansible-local' currently requires Ansible to be present on the
provisioned image.
The relevant issue to add an install option to the provisioner is:
https://github.com/mitchellh/packer/issues/2010
Until then, a notice similar to the 'puppet-masterless' and
'puppet-server' ones is added.
Changed the box from "chef/ubuntu-12.04" to "ubuntu/trusty64".
Changed the ruby version to 2.2.2 to accommodate the latest middleman.
Changed initialization from "bundle" to "make dev".
Changed the language of the vmware-iso floppy documentation to make is clearer that the deprecated ks=floppy syntax is a result of changes to Anaconda.
The vmware-iso example configuration to load a Kickstart configuration file off of a mounted floppy image is not valid for recent versions of Linux including RHEL7. The version of Anaconda used no longer supports ks=floppy.
This commit adds an alternative syntax that users can use with more recent version of Linux to source a Kickstart file from a mounted floppy image.
The Vagrant post processor expects the DO artifact ID to look like an
AWS artifact ID (region_id:snapshot_id). This commit makes the DO
artifact Id() function output this format.
David Zanetti
Hiroyuki MORITA
James Nugent
Sergey Bronnikov
Pierre-Etienne Poirot
Yuya YAGUCHI
Thach MAI
Chris Bednarski
Viktor Benei
michael
Jake Champlin
captainill
Mark Peek
Greg Baker
Andy Williams