[Module Proposal]: avm-ptn-subnet-nsg-routes

[Dylan-Prins]

Check for previous/existing GitHub issues/module proposals

• I have checked for previous/existing GitHub issues/module proposals.

Check this module doesn't already exist in the module indexes

• I have checked for that this module doesn't already exist in the module indexes.

Bicep or Terraform?

Bicep

Module Classification?

Pattern Module

Module Name

ptn/network/subnet-nsg-routes

Module Details

I want to create a module that creates a subnet with routes and security rules. This helps when you make use of landing zone vending, which only deploys a virtual network. I saw that there was an issue already for Terraform, but not for Bicep.

Do you want to be the owner of this module?

Yes

Module Owner's GitHub Username (handle)

Dylan-Prins

(Optional) Secondary Module Owner's GitHub Username (handle)

No response

[jtracey93]

Hey @Dylan-Prins

Thanks for the proposal.

Can you expand a little further about what the module will do and add value over using resource modules to do this.

E.g. provide a baseline of NSG rules and UDRs ?

This'll help us make a decision on the module proposal 👍

[Dylan-Prins]

Hi @jtracey93,

Actually I am looking for a template to use when i get a landingzone connected to a hub. The platform team is deploying the vnet with peering and i only want to deploy the subnets.

Now I use AVM for everything except deploying the subnets.

[jtracey93]

Ah okay that makes sense @Dylan-Prins

We are currently working on how we enable child modules for resource modules. This scenario would be covered when we have child modules available.

E.g. we will be able to publish the subnet as child module of the virtual network resource. Which will allow you to just deploy subnets.

Would you agree this would solve your challenge?

[Dylan-Prins]

@jtracey93 That would be a much better option! is there a ETA for the feature?

[jtracey93]

We are discussing it each week, but no ETA just yet. But I don't think its a long way off. We are meeting later today, let me ask and then check-in there and report back here.

cc: @matebarabas @AlexanderSehr @eriqua @ReneHezser

[AlexanderSehr]

+1 on @jtracey93's comment. If we publish a subnet pattern now, just to publish the corresponding resource module later, it may cause confusion - especially if they diverge.
That being said, if it turns out to take longer than hoped, then we can go ahead, and delist this module again later.

Regardless, I'd recommend to wait and for the time being rather use a plain resource implementation than publishing another module. Not my call though 😉