You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Currently, the module creates two route tables (internet-route and nat-route), only if the related gateways are created by the module.
We need to be able to create and manage route tables independently from gateway provisioning. This will enable support for Transit Routing configuration and other advanced design patterns.
The initial idea is to have a route table sub-module that can be called independently or from with the VCN module block.
Community Note
Description
Currently, the module creates two route tables (
internet-route
andnat-route
), only if the related gateways are created by the module.We need to be able to create and manage route tables independently from gateway provisioning. This will enable support for
Transit Routing
configuration and other advanced design patterns.The initial idea is to have a
route table
sub-module that can be called independently or from with the VCN module block.New or Affected Resource(s)
oci_core_route_table
Potential Terraform Configuration
Nothing yet. Module API needs to be defined.
# Copy-paste any Terraform configurations for how the requested feature may be used.
References
#37 would benefit from this feature.
The text was updated successfully, but these errors were encountered: