- 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.