Per Issue #6453, [email protected] targetting Windows was throwing the following error when setup as the docs instruct:
"Requested option use_tty was not defined in configuration"
This is caused by something in Ansible silently discarding the whole `DOCUMENTATION` string configuration when it can't parse it. The changed line in this PR fixes that. :)
to accept a list of strings (for Amazon builders).
Per this change, `temporary_security_group_source_cidr` in the configuration:
1. Will be renamed to `temporary_security_group_source_cidrs`.
2. Will accept a list of CIDRs.
3. Will have its documentation updated to reflect this change.
4. Will have a fixer attached for newer templates to avail of.
* removed packer.Cache and references since packer.Cache is never used except in the download step. The download step now uses the new func packer.CachePath(targetPath) for this, the behavior is the same.
* removed download code from packer that was reimplemented into the go-getter library: progress bar, http download restart, checksuming from file, skip already downloaded files, symlinking, make a download cancellable by context.
* on windows if packer is running without symlinking rights and we are getting a local file, the file will be copied instead to avoid errors.
* added unit tests for step_download that are now CI tested on windows, mac & linux.
* files are now downloaded under cache dir `sha1(filename + "?checksum=" + checksum) + file_extension`
* since the output dir is based on the source url and the checksum, when the checksum fails, the file is auto deleted.
* a download file is protected and locked by a file lock,
* updated docs
* updated go modules and vendors
Previously, if ami_block_device_mappings was set, and you were building
from an existing image, it would get silently ignored, and changing
root_device_name would be ignored. This changes that behaviour, so
if ami_block_device_mappings is specified, it's respected.
to retain current encryption settings
this changes the fields :
* ami_config.encrypt_boot
* block_device.encrypted
This also removes StepCreateEncryptedAMICopy as this step is now done in StepAMIRegionCopy
The example and description of pairing `vsphere` and `vsphere-template` in a JSON array is accurate but ought to be more spelled out.
This introduces a change which makes that part of the example and docs more verbose, hopefully mitigating potential confusion.
John Jones
Megan Marsh
Alvaro Miranda Aguilera
Adrien Delorme
Akshat Mahajan
Paul Meyer
Esten Rye
Adrien Delorme
Vadym Haidamaka
Matt Stofko
Sargun Dhillon
josepand
Davi Vidal
Anton Kvashenkin
Arnaud Dezandee
Miłosz Smółka
lrxcy
Elijah Caine M. Voigt