-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
[Bug]: aws_vpn_connection incorrect validation of inside_ipv6_cidr #36232
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.41.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Terraform Core Version
1.7.4
AWS Provider Version
5.39.1
Affected Resource(s)
Expected Behavior
tunnel1_inside_ipv6_cidr
andtunnel2_inside_ipv6_cidr
should accept all possible cidrs withinfd00::/8
.For example
fdff:1::1337:0:0/126
is withinfd00::/8
:Actual Behavior
tunnel1_inside_ipv6_cidr
andtunnel2_inside_ipv6_cidr
only accept cidrs withinfd00::/16
.Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
main.tf
file.terraform init
terraform plan
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
From the docs https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_VpnTunnelOptionsSpecification.html
And the incorrect regex validation that causes this error:
terraform-provider-aws/internal/service/ec2/vpnsite_connection.go
Line 1699 in c7c1bc3
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: