Feature: Separate resource group for DNS zones is not created by pipelines

[SvenAelterman]

Expected Behavior

It should be possible to specify the parPrivateDnsZonesResourceGroup parameter on the hub networking module and have the resource group created by the pipelines without further manual configuration.

Current Behavior

Hub networking module deployment fails because the resource group does not exist.

Possible Solution

Add an additional step in the pipelines to execute the connectivity resource group step again, with the different parameter value, to create the resource group.

Steps to Reproduce

1. Create Az DevOps/Bicep code using the Accelerator, version 3.0.1
2. In hubNetworking.parameters.all.json, add the parPrivateDnsZonesResourceGroup parameter and set it to a valid resource group name that's different from the "main" connectivity resource group name.
3. Execute the pipeline.

[oZakari]

Hi @SvenAelterman, thanks for submitting, we will be working on incorporating for the refactor with AVM modules which is anticipated to be released towards December.