-
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
[Bug]: custom tunnel*_inside_ipv6_cidr should not have dependency on the present of transit_gateway_id #36075
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
This functionality has been released in v5.42.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. |
Description
When specifying the "Inside IPv6 CIDR" for VPN tunnels, the provider requires specifying a Transit Gateway ID.
In the case of working with Cloud WAN attachment, the Transit Gateway is not necessary. thus, TF exit with error message
the corresponding CLI request to create the vpn_connection without specifying the transit gateway id but still able to provide tunnel options for custom inside IPc6 CIDR
response
Affected Resource(s) and/or Data Source(s)
aws_vpn_connection
Potential Terraform Configuration
No response
References
https://docs.aws.amazon.com/vpn/latest/s2svpn/create-cwan-vpn-attachment.html
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: