Add UDR option to route spoke traffic internally

[simonkurtz-MSFT]

Running bicep via AZD with routeSpokeTrafficInternally set to false (default) causes no change and maintains current behavior:

Running bicep via AZD with routeSpokeTrafficInternally set to true adds a new spoke-internal route:

Fixes #170

[kpantos]

Thank you so much @simonkurtz-MSFT for putting this together. Can you also please update the documentation with the new parameter that's added at the following documents:

• standalone-deployment-guide
• spoke deployment

So that users know they can change the LZA behavior?

Also, this needs to be implemented at the terraform side as well so that there's feature parity between implementations. Can you work on this too or should we assign someone else for it?

[simonkurtz-MSFT]

Hi @kpantos, thank you! I added to the standalone-deployment-guide but I did not see a section in the spoke deployment.

I would love to ask for help with Terraform as that is entirely out of my expertise, please.

[simonkurtz-MSFT]

Hi @kpantos, the most recent commit now supports internal routes when multiple VNet address prefixes are used. I validated these three combinations.

1. No internal routes

    "routeSpokeTrafficInternally": {
      "value":  false
    },   
    "spokeVNetAddressPrefixes": {
      "value":  ["10.1.0.0/22"]
    }

2. One internal route

    "routeSpokeTrafficInternally": {
      "value":  true
    },
    "spokeVNetAddressPrefixes": {
      "value":  ["10.1.0.0/22"]
    }

3. Multiple internal routes

    "routeSpokeTrafficInternally": {
      "value":  true
    },
    "spokeVNetAddressPrefixes": {
      "value":  ["10.1.0.0/22", "10.2.0.0/22"]
    }

[kpantos]

Awesome @simonkurtz-MSFT merged the pull request to the main branch.
Thank you so much for your effort.