Ajo Mathew Blog

Everything I have experienced and experimented on cloud and Deployments - Made by @Ajo Mathew.

© 2023. All rights reserved.

Azure DevOpos pipeline Yaml variables not substituting azureResourceManagerConnection

03 Mar 2022 Written by Ajo Mathew

While setting up an Azure ARM deployment pipeline using yaml. Below is my template.yaml file

parameters:

  - name: azRMConnection
    type: string
  - name: subscriptionID
    type: string
  - name: resourceGroupName
    type: string
  - name: deploymentLocation
    type: string
    default: "[resourceGroup().location]"
  - name: armTemplateFilePath
    type: string
  - name: armTemplateParameterFilePath
    type: string
  - name: overrideParameters
    type: string

steps:
  - task: AzureResourceManagerTemplateDeployment@3
    displayName: "ARM Template Deployment"
    inputs:
      deploymentScope: 'Resource Group'
      azureResourceManagerConnection: '$'
      deploymentMode: Incremental
      subscriptionId: $
      action: 'Create Or Update Resource Group'
      resourceGroupName: $
      location: $
      templateLocation: Linked artifact
      csmFile: $
      csmParametersFile: $
      overrideParameters: "$"

And this is my actual main.yaml looks like

stages:
  - stage: deployLogAnalytics
    displayName: "Deploying Basic component - OMS"
    pool:
      name: DP-DevTest
    jobs:
      - job:
        displayName: "Deploy Standard Components"
        variables:
          - group: 'Test-Infra-Pipeline'
        steps:
          - template: .\templates\deployARM.yaml
            parameters:
              azRMConnection: $(serviceConnection)
              subscriptionID: $(subscriptionID)
              resourceGroupName: $(resourceGroup)
              deploymentLocation: $(deploymentLocation)
              armTemplateFilePath: $(Build.Repository.LocalPath)\ARMTemplates\AzureLogAnalytics\logAnalytics.json
              armTemplateParameterFilePath: $(Build.Repository.LocalPath)\ARMTemplates\AzureLogAnalytics\logAnalytics.parameters.json
              overrideParameters: -envId $(envId) -vnetName $(vnetName) -subnetName $(subnetName) -networkResourceGroup $(networkResourceGroup)

Variable serviceConnection is defined in Variable groups and referenced by pipeline yaml file. While the pipeline runs it does not transform to actual value.

Azure DevOps is unable to parse the variable $(serviceConnection) but directly pass the value to task. This issue or similar reported as a bug in github

As a work around we have to hard code the connection string name in our main or azure-pipeline yaml file as shown below

And this is my actual main.yaml looks like

variables:
  - group: 'Pipeline-vars'
  - name: serviceConnection
    value: $[replace(replace(eq(variables['azServiceConnection'],'prod'), 'True', 'prod-connection'), 'False', 'dev-connection')]

stages:
  - stage: deployLogAnalytics
    displayName: "Deploying Basic component - OMS"
    pool:
      name: DP-DevTest
    jobs:
      - job:
        displayName: "Deploy Standard Components"
        variables:
          - group: 'Test-Infra-Pipeline'
        steps:
          - template: .\templates\deployARM.yaml
            parameters:
              azRMConnection: $(serviceConnection)
              subscriptionID: $(subscriptionID)
              resourceGroupName: $(resourceGroup)
              deploymentLocation: $(deploymentLocation)
              armTemplateFilePath: $(Build.Repository.LocalPath)\ARMTemplates\AzureLogAnalytics\logAnalytics.json
              armTemplateParameterFilePath: $(Build.Repository.LocalPath)\ARMTemplates\AzureLogAnalytics\logAnalytics.parameters.json
              overrideParameters: -envId $(envId) -vnetName $(vnetName) -subnetName $(subnetName) -networkResourceGroup $(networkResourceGroup)

Related posts