Bot releases are visible (Hide)
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.3.1...v1.3.2
Published by github-actions[bot] 8 months ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.3.0...v1.3.1
Published by github-actions[bot] 9 months ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.9...v1.3.0
Published by github-actions[bot] 10 months ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.8...v1.2.9
Published by github-actions[bot] 11 months ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.7...v1.2.8
Published by github-actions[bot] about 1 year ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.6...v1.2.7
Published by github-actions[bot] over 1 year ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.5...v1.2.6
Published by github-actions[bot] over 1 year ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.4...v1.2.5
Published by github-actions[bot] over 1 year ago
As part of the fixes related to the regression from 1.2.3, when one changes the value of the associate_public_ip_address
, the plugin will attempt to get the default VPC for the account that runs the build, should none be specified. To do so, we use the DescribeVpcs
API endpoint, which may cause builds to fail because of a missing permission: ec2:DescribeVpcs
.
We are actively working on a fix for this, so the default behaviour in case the permission is missing will not make builds fail, but instead show a warning regarding the associate_public_ip_address
being ignored, as was silently the case before version 1.2.3.
In the meantime, you may either specify a subnet/VPC, or remove the associate_public_ip_address
from your configuration if you encounter this error.
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.3...v1.2.4
Published by github-actions[bot] over 1 year ago
A regression to the subnet selection logic when using the subnet_id
or subnet_filter
along with the associate_public_ip_address
configuration argument was introduced in release v1.2.3. A fix has been made and is available for use in v1.2.4.
We recommend that you upgrade to the latest available release prior to running a new Packer build. If you are not using associate_public_ip_address
or running an older version of the packer-plugin-amazon
plugin no change is necessary.
packer {
required_plugins {
amazon = {
version = ">=1.2.4"
source = "github.com/hashicorp/amazon"
}
}
}
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.2...v1.2.3
Published by github-actions[bot] over 1 year ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.1...v1.2.2
Published by github-actions[bot] over 1 year ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.2.0...v1.2.1
Published by github-actions[bot] almost 2 years ago
Note on the breaking change: the commit merged from PR #309 fixes a bug where the plugin would fallback on the private IP after a single try to get the public IP of the instance being created. Now, it will try multiple times to get the public IP, and only on the latest try, if the public IP is still unavailable, will it fallback to the private IP of the instance. While this behaviour is in line with the documentation, this may be surprising to users that encounter this behaviour, as with this update, there's a greater chance of the IP being the public one. For this reason, we have marked it as breaking, and updated the minor version of the plugin to highlight this change.
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.1.6...v1.2.0
Published by github-actions[bot] almost 2 years ago
uefi_data
in builders by @Marcelotsvaz in https://github.com/hashicorp/packer-plugin-amazon/pull/272
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.1.5...v1.1.6
Published by github-actions[bot] about 2 years ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.1.4...v1.1.5
Published by github-actions[bot] about 2 years ago
enable_nitro_enclave
argument to enable support for Nitro Enclaves on instance by @SajanAlexander-okta in https://github.com/hashicorp/packer-plugin-amazon/pull/257
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.1.3...v1.1.4
Published by github-actions[bot] about 2 years ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.1.2...v1.1.3
Published by github-actions[bot] over 2 years ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.1.1...v1.1.2
Published by github-actions[bot] over 2 years ago
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.1.0...v1.1.1
Published by github-actions[bot] over 2 years ago
This release contains the latest golang.org/x/crypto/ssh module which implements client authentication support for signature algorithms based on SHA-2 for use with existing RSA keys. Previously, a client would fail to authenticate with RSA keys to servers that reject signature algorithms based on SHA-1.
Full Changelog: https://github.com/hashicorp/packer-plugin-amazon/compare/v1.0.9...v1.1.0