Parameters files for bicep deployment #684

mlunetta · 2022-09-29T15:14:42Z

mlunetta
Sep 29, 2022

Hi folks,

I'm trying to deploy some stuff with AzOps using bicep, but without success.

Basically, I want to create 1 resource group and some other resources inside this resource group.
I created a subfolder in my lz subscription, representing the new resource group and some bicep files with a parameter file, in this format:

Below my bicep and parameter files content:
main.bicep

targetScope = 'subscription'

param appname string
param environment string
param vnetAddrPrefix array
param subnetAddrPrefix string
param rg_name string = 'rg-${appname}-${environment}-network'
param location string = 'westeurope'

var nsgname = 'nsg-${appname}-${environment}'
var vnetname = 'vnet-${appname}-${environment}'
var subnetname = 'snet01'

resource resourceGroup 'Microsoft.Resources/resourceGroups@2021-04-01' = {
  name: rg_name
  location: location
}

module nsg 'nsg.bicep' = {
  scope: resourceGroup
  name: nsgname
  params: {
    location: location
    name: nsgname
  }
}

module vnet 'vnet.bicep' = {
  scope: resourceGroup
  name: vnetname
  params: {
    location: location
    nsgId: nsg.outputs.nsgId
    subnetAddrPrefix: subnetAddrPrefix
    subnetName: subnetname
    vnetAddrPrefix: vnetAddrPrefix
    vnetName: vnetname
  }
}

nsg.bicep

param name string
param location string

resource networkSecurityGroup 'Microsoft.Network/networkSecurityGroups@2019-11-01' = {
  name: name
  location: location
  properties: {
    securityRules: [
    ]
  }
}

output nsgId string = networkSecurityGroup.id

vnet.bicep

param vnetName string
param vnetAddrPrefix array
param subnetName string
param subnetAddrPrefix string
param location string
param nsgId string

resource virtualNetwork 'Microsoft.Network/virtualNetworks@2019-11-01' = {
  name: vnetName
  location: location
  properties: {
    addressSpace: {
      addressPrefixes: vnetAddrPrefix
    }
    subnets: [
      {
        name: subnetName
        properties: {
          addressPrefix: subnetAddrPrefix
          networkSecurityGroup: {
            id: nsgId
          }
        }
      }
    ]
  }
}

main.parameters.json

{
    "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
      "appname": {
        "value": "app01"
      },
      "environment": {
        "value": "dev"
      },
      "vnetAddrPrefix":{
        "value":
          [
            "10.0.0.0/16"
          ]
      },
      "subnetAddrPrefix":{
        "value": "10.0.0.0/27"
      }
    }
  }

The push fails with this error:

[10:49:03][Invoke-AzOpsPush] Deployment required
[10:49:03][Invoke-AzOpsPush] Adding or modifying:
[10:49:03][Invoke-AzOpsPush]   root/beta (beta)/beta-landingzones (beta-landingzones)/beta-online (beta-online)/lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)/rg-app01-dev-network/main.parameters.json
[10:49:03][Invoke-AzOpsPush]   templates/landingzone-blueprint/bicep/rg-$appname-$env-network/main.parameters.json
[10:49:03][Invoke-AzOpsPush] Deleting:
WARNING: [10:49:05][AzOpsScope] Unable to determine type from Template or Template Parameter file: /home/runner/work/AzOps[100](https://github.com/mlunetta/AzOps10052022/actions/runs/3150658517/jobs/5123700438#step:4:103)52022/AzOps10052022/root/beta (beta)/beta-landingzones (beta-landingzones)/beta-online (beta-online)/lz-prod-001 (8e8af[102](https://github.com/mlunetta/AzOps10052022/actions/runs/3150658517/jobs/5123700438#step:4:105)-d409-4bcc-bdab-c52a33b4aa0b)/rg-app01-dev-network/main.parameters.json
[10:49:06][New-AzOpsDeployment] Processing deployment AzOps-main.parameters-B9EE for template /home/runner/work/AzOps10052022/AzOps10052022/root/beta (beta)/beta-landingzones (beta-landingzones)/beta-online (beta-online)/lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)/rg-app01-dev-network/main.bicep with parameter "/home/runner/work/AzOps10052022/AzOps10052022/root/beta (beta)/beta-landingzones (beta-landingzones)/beta-online (beta-online)/lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)/rg-app01-dev-network/main.parameters.json" in mode Incremental
WARNING: [10:49:06][AzOpsScope] Unable to determine type from Template or Template Parameter file: /home/runner/work/AzOps10052022/AzOps10052022/root/beta (beta)/beta-landingzones (beta-landingzones)/beta-online (beta-online)/lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)/rg-app01-dev-network/main.parameters.json
ConvertFrom-Json: Conversion from JSON failed with error: Error parsing boolean value. Path '',
line 1, position 1.

Error: Process completed with exit code 1.

Is this something related to the parameters file naming or similar?

Thanks!

Answered by daltondhcp

Oct 3, 2022

Hi @mlunetta,

Took a closer look at this and now understand why it fails.
The template main.bicep's targetScope is subscription as you are creating a resource group, but you are submitting it to a resource group folder that doesn't exist yet.
To make it work, you need to add the template/parameter file directly under the subscription folder/scope (lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)), as the target scope for the deployment is determined based on the folder structure.

Hope this helps.

/Johan

View full answer

daltondhcp · 2022-09-30T08:41:49Z

daltondhcp
Sep 30, 2022
Maintainer

As you can see on this line [10:49:06][New-AzOpsDeployment] Processing deployment AzOps-main.parameters-B9EE for template /home/runner/work/AzOps10052022/AzOps10052022/root/beta (beta)/beta-landingzones (beta-landingzones)/beta-online (beta-online)/lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)/rg-app01-dev-network/main.bicep with parameter "/home/runner/work/AzOps10052022/AzOps10052022/root/beta (beta)/beta-landingzones (beta-landingzones)/beta-online (beta-online)/lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)/rg-app01-dev-network/main.parameters.json" in mode Incremental, parameter files following the <templateFileName>.parameters.json convention will automatically be used for deployment.

Based on the error message, it looks like the parameter file might not be valid (your snippet looks valid). Can you verify that it works to deploy it manually with CLI or PowerShell?

1 reply

mlunetta Sep 30, 2022
Author

I've tested it with CLI and it works correctly:

az deployment sub 
create --name bicepTestDeployment30092022 --location westeurope --template-file main.bicep --parameters @main.parameters.json
A new Bicep release is available: v0.10.61. Upgrade now by running "az bicep upgrade".
{
  "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/providers/Microsoft.Resources/deployments/bicepTestDeployment30092022",
  "location": "westeurope",
  "name": "bicepTestDeployment30092022",
  "properties": {
    "correlationId": "d84c3885-3a1c-4cd2-b4f9-4d2491bccaca",
    "debugSetting": null,
    "dependencies": [
      {
        "dependsOn": [
          {
            "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network",
            "resourceName": "rg-app01-dev-network",
            "resourceType": "Microsoft.Resources/resourceGroups"
          }
        ],
        "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network/providers/Microsoft.Resources/deployments/nsg-app01-dev",
        "resourceGroup": "rg-app01-dev-network",
        "resourceName": "nsg-app01-dev",
        "resourceType": "Microsoft.Resources/deployments"
      },
      {
        "dependsOn": [
          {
            "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network/providers/Microsoft.Resources/deployments/nsg-app01-dev",
            "resourceGroup": "rg-app01-dev-network",
            "resourceName": "nsg-app01-dev",
            "resourceType": "Microsoft.Resources/deployments"
          },
          {
            "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network",
            "resourceName": "rg-app01-dev-network",
            "resourceType": "Microsoft.Resources/resourceGroups"
          }
        ],
        "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network/providers/Microsoft.Resources/deployments/vnet-app01-dev",
        "resourceGroup": "rg-app01-dev-network",
        "resourceName": "vnet-app01-dev",
        "resourceType": "Microsoft.Resources/deployments"
      }
    ],
    "duration": "PT36.3630346S",
    "error": null,
    "mode": "Incremental",
    "onErrorDeployment": null,
    "outputResources": [
      {
        "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network"
      },
      {
        "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network/providers/Microsoft.Network/networkSecurityGroups/nsg-app01-dev",
        "resourceGroup": "rg-app01-dev-network"
      },
      {
        "id": "/subscriptions/bfbd5246-5e2d-45a7-a9bb-28e4f550184b/resourceGroups/rg-app01-dev-network/providers/Microsoft.Network/virtualNetworks/vnet-app01-dev",
        "resourceGroup": "rg-app01-dev-network"
      }
    ],
    "outputs": null,
    "parameters": {
      "appname": {
        "type": "String",
        "value": "app01"
      },
      "environment": {
        "type": "String",
        "value": "dev"
      },
      "location": {
        "type": "String",
        "value": "westeurope"
      },
      "rg_name": {
        "type": "String",
        "value": "rg-app01-dev-network"
      },
      "subnetAddrPrefix": {
        "type": "String",
        "value": "10.0.0.0/27"
      },
      "vnetAddrPrefix": {
        "type": "Array",
        "value": [
          "10.0.0.0/16"
        ]
      }
    },
    "parametersLink": null,
    "providers": [
      {
        "id": null,
        "namespace": "Microsoft.Resources",
        "providerAuthorizationConsentState": null,
        "registrationPolicy": null,
        "registrationState": null,
        "resourceTypes": [
          {
            "aliases": null,
            "apiProfiles": null,
            "apiVersions": null,
            "capabilities": null,
            "defaultApiVersion": null,
            "locationMappings": null,
            "locations": [
              "westeurope"
            ],
            "properties": null,
            "resourceType": "resourceGroups",
            "zoneMappings": null
          },
          {
            "aliases": null,
            "apiProfiles": null,
            "apiVersions": null,
            "capabilities": null,
            "defaultApiVersion": null,
            "locationMappings": null,
            "locations": [
              null
            ],
            "properties": null,
            "resourceType": "deployments",
            "zoneMappings": null
          }
        ]
      }
    ],
    "provisioningState": "Succeeded",
    "templateHash": "7304019574854355375",
    "templateLink": null,
    "timestamp": "2022-09-30T09:38:50.879804+00:00",
    "validatedResources": null
  },
  "tags": null,
  "type": "Microsoft.Resources/deployments"
}

daltondhcp · 2022-09-30T14:06:09Z

daltondhcp
Sep 30, 2022
Maintainer

Thank you for the response! I will try to reproduce your issue to understand why it fails then.

0 replies

daltondhcp · 2022-10-03T17:01:16Z

daltondhcp
Oct 3, 2022
Maintainer

Hi @mlunetta,

Took a closer look at this and now understand why it fails.
The template main.bicep's targetScope is subscription as you are creating a resource group, but you are submitting it to a resource group folder that doesn't exist yet.
To make it work, you need to add the template/parameter file directly under the subscription folder/scope (lz-prod-001 (8e8af102-d409-4bcc-bdab-c52a33b4aa0b)), as the target scope for the deployment is determined based on the folder structure.

Hope this helps.

/Johan

1 reply

mlunetta Oct 5, 2022
Author

Hi @daltondhcp,

Per your suggestion, I've tried to add my bicep files under the subscription folder, and now it works as expected!
Thank you very much for your help!

All the best,
Marcantonio

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Parameters files for bicep deployment #684

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 3 comments 2 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Parameters files for bicep deployment #684

mlunetta Sep 29, 2022

Replies: 3 comments · 2 replies

daltondhcp Sep 30, 2022 Maintainer

mlunetta Sep 30, 2022 Author

daltondhcp Sep 30, 2022 Maintainer

daltondhcp Oct 3, 2022 Maintainer

mlunetta Oct 5, 2022 Author

mlunetta
Sep 29, 2022

Replies: 3 comments 2 replies

daltondhcp
Sep 30, 2022
Maintainer

mlunetta Sep 30, 2022
Author

daltondhcp
Sep 30, 2022
Maintainer

daltondhcp
Oct 3, 2022
Maintainer

mlunetta Oct 5, 2022
Author