fixed bug in vnet peering (#136)

docs/reference/enterpriseScaleAnalytics.bicep

@@ -223,7 +223,7 @@ resource dataLandingZoneDeployment 'Microsoft.Resources/deployments@2021-04-01'
 }]
 
 module vnetPeeringDeployment 'modules/vnetPeeringOrchestration.bicep' = [for index1 in range(0, length(dataLandingZoneDetails)): {
-  name: 'vnetPeeringDeployment${index1}'
+  name: 'vnetPeeringDeployment-${index1}-${deployment().location}'
   scope: subscription()
   params: {
     sourceVnetId: reference(dataLandingZoneDeployment[index1].name).outputs.vnetId.value

docs/reference/enterpriseScaleAnalytics.json

@@ -5,7 +5,7 @@
     "_generator": {
       "name": "bicep",
       "version": "0.4.451.19169",
-      "templateHash": "880387641665577441"
+      "templateHash": "10324138329887264373"
     }
   },
   "parameters": {
@@ -273,7 +273,7 @@
       },
       "type": "Microsoft.Resources/deployments",
       "apiVersion": "2019-10-01",
-      "name": "[format('vnetPeeringDeployment{0}', range(0, length(parameters('dataLandingZoneDetails')))[copyIndex()])]",
+      "name": "[format('vnetPeeringDeployment-{0}-{1}', range(0, length(parameters('dataLandingZoneDetails')))[copyIndex()], deployment().location)]",
       "location": "[deployment().location]",
       "properties": {
         "expressionEvaluationOptions": {