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
Is your feature request related to an issue?
No
We are currently vending our subscriptions and that includes a rg, vnet and a routetable, but that I've built as a separate component using the azapi_resource resource. But I think that from a platform team perspective the routetable resource is as close to the vnet as it can be and should not be something that should differ from any other vending-component.
Describe the solution you'd like
Have a separate module that I can vendor the routetable directly with the Azure/lz-vending/azurerm//modules/virtualnetwork module (or a separate one).
Additional context
This is how I've solved it as of today (don't have the locals and data sources included).
A side note as well, we do have hub_peering_enabled = true and hub_peering_use_remote_gateways = false in terms what we have under the var.virtual_networks of virtualnetwork-module.
The text was updated successfully, but these errors were encountered:
Thanks for raising. I think that this is a valid ask, we will add it to the backlog but would also love to receive a PR.
We intend to revamp this module to use azapi 2 in the new year so I was holding off any feature requests until then. However if you want to raise one against the as-is then I'd be happy to review! #RR
Description
Is your feature request related to an issue?
No
We are currently vending our subscriptions and that includes a rg, vnet and a routetable, but that I've built as a separate component using the
azapi_resource
resource. But I think that from a platform team perspective the routetable resource is as close to the vnet as it can be and should not be something that should differ from any other vending-component.Describe the solution you'd like
Have a separate module that I can vendor the routetable directly with the Azure/lz-vending/azurerm//modules/virtualnetwork module (or a separate one).
Additional context
This is how I've solved it as of today (don't have the locals and data sources included).
A side note as well, we do have
hub_peering_enabled = true
andhub_peering_use_remote_gateways = false
in terms what we have under the var.virtual_networks of virtualnetwork-module.The text was updated successfully, but these errors were encountered: