You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The example assumes you are using a [`bicepconfig.json`](https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-config) configuration file like:
195
+
196
+
```json
197
+
{
198
+
"moduleAliases": {
199
+
"br": {
200
+
"modules": {
201
+
"registry": "<registryName>.azurecr.io",
202
+
"modulePath": "bicep/modules"
203
+
}
204
+
}
205
+
}
206
+
}
207
+
```
208
+
209
+
194
210
### ***Example with template-specs***
195
211
196
212
The following example shows how you could orchestrate a deployment of multiple resources using template specs. In this example we will deploy a NSG and use the same in a subsequent VNET deployment.
197
213
198
214
```bicep
215
+
targetScope = 'subscription'
216
+
199
217
// ================ //
200
218
// Input Parameters //
201
219
// ================ //
202
220
221
+
// RG parameters
222
+
@description('Optional. The name of the resource group to deploy')
223
+
param resourceGroupName string = 'validation-rg'
224
+
225
+
@description('Optional. The location to deploy into')
226
+
param location string = deployment().location
227
+
203
228
// Network Security Group parameters
204
229
@description('Optional. The name of the vnet to deploy')
The example assumes you are using a [`bicepconfig.json`](https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/bicep-config) configuration file like:
0 commit comments