-
Notifications
You must be signed in to change notification settings - Fork 9.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resource/aws_vpc: Set ipv6 properties even if no ipv6 is enabled to allow usage in conditionals (fixes #688) #2103
Conversation
…in conditionals (fixes #688)
@radeksimko Can this be merged? |
@Ninir Do you have any opinion on this? I'd like to get this released in order to resolve terraform-aws-modules/terraform-aws-vpc#21 |
Are there any updates for this from Terraform's side? |
hashicorp#2103 * resource/aws_vpc: Set ipv6 properties even if no ipv6 is enabled to allow usage in conditionals (fixes hashicorp#688) hashicorp#2103
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm very sorry this didn't get pulled in earlier. I believe it was waiting for Terraform 0.12 related updates however, we do this same logic other places so I'm going to pull this in for consistency.
This has been released in version 1.43.1 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
Thanks, Brian! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
This sets IPv6-related attributes of a VPC to empty-string instead of leaving them undefined in case the VPC doesn't have VPC enabled. This allows us to use the attributes in a conditional as described in #688.
In a way, this feels like a very specific workaround for hashicorp/hil#50. However, it might help some people creating modules where IPv6-support is optional.
Feel free to reject this PR if you feel it adds more tech-debt than value.