-
-
Notifications
You must be signed in to change notification settings - Fork 234
fix: Use IPv6 CIDR block destination on route when IPv6 support is enabled #102
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
fix: Use IPv6 CIDR block destination on route when IPv6 support is enabled #102
Conversation
This PR has been automatically marked as stale because it has been open 30 days |
"Keep alive" post |
This PR has been automatically marked as stale because it has been open 30 days |
"Keep alive" post |
This PR has been automatically marked as stale because it has been open 30 days |
"Keep alive" post |
This PR has been automatically marked as stale because it has been open 30 days |
"Keep alive" post"Keep alive" post |
This PR has been automatically marked as stale because it has been open 30 days |
"Keep alive" post |
This PR has been automatically marked as stale because it has been open 30 days |
"Keep alive" post |
This PR has been automatically marked as stale because it has been open 30 days |
"Keep alive" post |
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.
thank you
### [2.12.1](v2.12.0...v2.12.1) (2023-12-11) ### Bug Fixes * Use IPv6 CIDR block destination on route when IPv6 support is enabled ([#102](#102)) ([f70ec98](f70ec98))
This PR is included in version 2.12.1 🎉 |
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
Make route creation use
aws_route.destination_ipv6_cidr_block
for attachments withipv6_support
set totrue
.Motivation and Context
Creating routes for TGW attachments breaks the generally working support for IPv6 based setups.
vpc_attachments[].vpc_route_table_ids
fails #101vpc_attachments[].vpc_route_table_ids
fails #112Breaking Changes
There should be no negative effect on backwards compatibility with the current major version.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull request