Open johnalotoski opened 1 month ago
Voting for Prioritization
Volunteering to Work on This Issue
I wrote #37262 for this, I couldn't get any traction. It doesn't look like its totally bitrotted yet.
I wrote #37262 for this, I couldn't get any traction. It doesn't look like its totally bitrotted yet.
Oh, that would be great to get merged! Let's see if we can get a few more :+1: to help get it moving.
Will that PR also cover the use case of switching from a declared ipv6_address_count
with no declared ipv6_addresses
list/set to only a declared ipv6_addresses
list/set without a forced re-create?
Terraform Core Version
OpenTofu 1.7.1
AWS Provider Version
5.66.0
Affected Resource(s)
aws_instance
which has already been configured with anipv6_address_count
of1
to obtain an auto-assigned ipv6 is then changed to a single declared static ipv6 of $CUSTOM_IPV6 using:ipv6_addresses
oftolist(["$CUSTOM_IPV6"])
Expected Behavior
The auto-assigned ipv6 should be updated to the explicitly declared ipv6. The instance should not be force replaced. Unassignment of an auto-assigned ipv6 with application of a custom ipv6 can be performed through the aws console UI without destroying the instance.
Actual Behavior
The instance will be force replaced.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
ipv6_address_count
of1
ipv6_address_count
and addipv6_addresses
oftolist(["$CUSTOM_IPV6"])
Debug Output
No response
Panic Output
Important Factoids
No response
References
A similar issue appears to have been reported in #33707 which led to fixing of the force replacement on adjusting
ipv6_address_count
oripv6_addresses
, although it does not fix force replacement by switching from one to the other. Going from auto-assigned ipv6 to static declared ipv6 or vice-versa may be a common, or at least not rare, use case.Would you like to implement a fix?
No