Closed lucasvuotto closed 2 years ago
This PR is included in version 3.3.0 :tada:
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Description
Added an output for the
ipv6_addresses
of the AWS instances, similar to bothpublic_ip
andprivate_ip
.Motivation and Context
Motivation is the same as #241 . In particular, relying on
aws_instance
data source overly complicates working with IPv6 if usingcount
orfor_each
in the module, having to split apply into 2 steps: one targeted for this module's instances, another one for the rest of the stuff, as you can't use a dynamicfor_each
in a data source:This is particular handy when the subnet the instance is placed in assigns IPv6 addresses at creation time, as neither
ipv6_addresses
oripv6_addresses_count
are required to be set in that case to get an IPv6 address.Do note that
aws_spot_instance_request
resource doesn't offer a similar attribute, hence it isn't covered in this PR.Breaking Changes
How Has This Been Tested?
examples/*
projects