[AVM Module Issue]: Allow BYO subnets and do not require almost all subnets to be created

[JyrkiHei]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Feature Request

(Optional) Module Version

0.4.0

(Optional) Correlation Id

No response

Description

BYO VNET is supported already, but it would be nice to support also BYO SUBNETs. We are creating VNET in subscription vending process and creating some other resources before we would run this module. Other resources include multiple subnets, NSGs and route tables + other services. We would like to create all subnets in one place and could pass these as a reference to this module. We could probably somehow work with current implementation and create subnets in two different places but it could get messy if even technically possible.

Also some of the subnets are mandatory in this module even though those would not be necessarily used at all (like APIMSubnet, AppGatewaySubnet, DevOpsBuildSubnet)

[microsoft-github-policy-service]

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the Terraform Issue Triage documentation.

[microsoft-github-policy-service]

Warning

Tagging the AVM Core Team (@Azure/avm-core-team-technical-terraform) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

Tip

• To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
• To avoid this rule being (re)triggered, the ""Needs: Triage 🔍" label must be removed as part of the triage process (when the issue is first responded to)!