Update tier3.bicep Creation in correct Subscription (#726)

Tier3s don't get created in the target subscription. Instead, they get created the -currently logged on- subscription. This update will correct that and close issue #724

Co-authored-by: lisamurphy-msft <87032539+lisamurphy-msft@users.noreply.github.com>
This commit is contained in:
LManning-Dev 2022-08-29 10:53:24 -04:00 коммит произвёл GitHub
Родитель 9a63fa4beb
Коммит 33a21d1444
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
1 изменённых файлов: 3 добавлений и 1 удалений

Просмотреть файл

@ -119,6 +119,7 @@ var calculatedTags = union(tags, defaultTags)
module resourceGroup '../../modules/resource-group.bicep' = {
name: workloadResourceGroupName
scope: subscription(workloadSubscriptionId)
params: {
name: workloadResourceGroupName
location: location
@ -128,7 +129,7 @@ module resourceGroup '../../modules/resource-group.bicep' = {
module spokeNetwork '../../core/spoke-network.bicep' = {
name: 'spokeNetwork'
scope: az.resourceGroup(resourceGroup.name)
scope: az.resourceGroup(workloadSubscriptionId, resourceGroup.name)
params: {
tags: calculatedTags
location:location
@ -157,6 +158,7 @@ module spokeNetwork '../../core/spoke-network.bicep' = {
module workloadVirtualNetworkPeerings '../../core/spoke-network-peering.bicep' = {
name: take('${workloadName}-to-hub-vnet-peering', 64)
scope: subscription(workloadSubscriptionId)
params: {
spokeName: workloadName
spokeResourceGroupName: resourceGroup.name