Adding credentials to a file that may get committed to
a git repository is dangerous; make the example follow
best practices and pull the AWS credentials out of
the environment
- 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
Chris Peterson
Marc Abramowitz
Asfand Yar Qazi
Andrew Starr-Bochicchio
Chris Bednarski
Ian Duffy
BetaGrumm
Dan Buch
YAMADA Tsuyoshi
Cameron Stokes
David Zanetti
Hiroyuki MORITA
James Nugent
Sergey Bronnikov