-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
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
feat: Add support for multiple route tables to public and intra subnets #1051
feat: Add support for multiple route tables to public and intra subnets #1051
Conversation
@bryantbiggs Any interest in introducing this feature to the module? I'm happy to update the examples and finalize this PR if this is something you'd be open to merging. |
tf-controller plan output: No changes. Your infrastructure matches the configuration.
Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.
To apply this plan, please merge this pull request. |
Any movements on this? Would love to have it. |
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 don't think this accomplishes the very original ask, but ok 😬
## [5.8.0](v5.7.2...v5.8.0) (2024-04-25) ### Features * Add support for multiple route tables to public and intra subnets ([#1051](#1051)) ([da05f24](da05f24))
This PR is included in version 5.8.0 🎉 |
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
Support for multiple route tables when creating public and intra subnets.
Motivation and Context
Guarantee that the used route table for public and intra subnets on creation is different when a boolean variable is set to true.
Breaking Changes
No breaking changes, as the variables are optional and defaulted to
false
.How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectspre-commit run -a
on my pull requestChanges were tested in a staging environment where existing public and intra subnets and route tables existed. Multiple route tables were enabled for both public and intra subnets. The existing route tables and associations were successfully updated and network traffic continued to flow as normal.