💡 Feature Request - Add next hop and route table

[reduards]

Describe the solution you'd like

Looked at the ALZ-Bicep Orchestration - hubPeeredSpoke module and it contains route table creation with nexthop to the firewall. Think that should be added in the vending module as well for the corp landing zones.

Additional context

Add any other context or screenshots about the feature request here. 📷

[jtracey93]

Thanks for the request @reduards.

I will discuss with @matt-FFFFFF when he returns from OOF as he maintains the TF module equivalent and we would like to keep these in feature parity where possible.

Thanks

[reduards]

Great, I think for corp it would make sense, together with the policy of enforcing route table on subnet creation. Considering making this policy default similiar to the policy enforcing NSG could be considered as well.

[jtracey93]

Hey @reduards,

As we don't create any subnets today in these modules, as documented, would you want this just to be created so available to associate to app teams etc.?

Also, what option would you want from the below options:

1. Create UDR with a single default route (0.0.0.0/0) to a next hop IP address, that we would take in as a parameter value
2. Create a UDR with as many routes as you with in a complex array/object definition?

Let us know

P.S. we try to keep these modules disconnected from ALZ directly so as many people as possible can use them. Whether they use ALZ or not 👍 But to your mention about the UDR policy, it is unlikely we would add that to ALZ as not all customers use NVAs etc and some just use native routing 👍

[reduards]

Hey @jtracey93,

Yes, I am thinking that this can be created so it is available for app teams to associate with subnet and that this could be then enforced with policy as well (Subnet needs to be associated with route table).

Would suggest 2. for flexibility but with 1. as the leading example.

Best Regards,
Rasmus

[stalejohnsen]

Option 2 sounds great!