Search for a command to run...
I used to be a .NET developer. Nowaways, I am a DevOps solutions architect with a focus on Azure and Kubernetes.
I also love productivity topics, especially when it comes to doing more with less of my time. I'm also a daddy, so time is a limited resource for me.
No comments yet. Be the first to comment.
I'm going to share all my secrets with you
Using a pull-request workflow
This is the guide I wish I had
Connecting your GitHub Workflows to Azure AD using OpenID Connect
In this post, I’ll walk through the essentials of configuring an AKS cluster to use Argo CD with an NGINX Ingress Controller. Pre-Requisites You’ll need: An AKS cluster. Here’s a Gist I use to create a simple cluster. Helm 3 Azure CLI A Custom DNS/A...
Deploying Azure Resource Manager (ARM) templates from Azure DevOps is very powerful. It encourages developers and operators to maintain a declarative file describing the infrastructure on Azure. Also helps prevent pesky environment drifts because of someone clicking from the portal to make changes. But, deploying these ARM templates can be daunting. Here’s some tips.
Assuming you have an ARM template ready and committed to a repository, you’ll want to start with adding the Azure Resource Group Deployment task
In YAML, your task could look like this:
- task: AzureResourceGroupDeployment@2
displayName: Deploy ARM Template to Create CDN
inputs:
azureSubscription: $(azureServiceEndpoint)
action: 'Create Or Update Resource Group'
resourceGroupName: $(resourceGroup)
location: 'East US'
templateLocation: 'Linked artifact'
csmFile: '$(Pipeline.Workspace)/drop/arm/cdn-blob.json'
overrideParameters: '-environment $(environment) -appName $(spaNameNoDashes)'
deploymentMode: 'Incremental'
It’s often useful to use ARM template output variables so that you can use those variables from subsequent tasks.
For example:
After having assigned output variables, you can read them from the pipeline by specifying a name for the outputVariable. For instance:
- task: AzureResourceGroupDeployment@2
displayName: Deploy ARM Template to Create CDN
inputs:
azureSubscription: $(azureServiceEndpoint)
action: 'Create Or Update Resource Group'
resourceGroupName: $(resourceGroup)
location: 'East US'
templateLocation: 'Linked artifact'
csmFile: '$(Pipeline.Workspace)/drop/arm/cdn-blob.json'
overrideParameters: '-environment $(environment) -appName $(spaNameNoDashes)'
deploymentMode: 'Incremental'
deploymentOutputs: 'ArmOutputs'
Using Powershell, you could use the following script:
function Convert-ArmOutputToPsObject {
param (
[Parameter(Mandatory=$true)]
[string]
$ArmOutputString
)
if ($PSBoundParameters['Verbose']) {
Write-Host "Arm output json is:"
Write-Host $ArmOutputString
}
$armOutputObj = $ArmOutputString | ConvertFrom-Json
$armOutputObj.PSObject.Properties | ForEach-Object {
$type = ($_.value.type).ToLower()
$keyname = "ArmOutputs.$($_.name)"
$value = $_.value.value
if ($type -eq "securestring") {
Write-Host "##vso[task.setvariable variable=$keyname;issecret=true]$value"
Write-Host "Added Azure DevOps secret variable '$keyname' ('$type')"
} elseif ($type -eq "string") {
Write-Host "##vso[task.setvariable variable=$keyname]$value"
Write-Host "Added Azure DevOps variable '$keyname' ('$type') with value '$value'"
} else {
Throw "Type '$type' is not supported for '$keyname'"
}
}
}
So from the pipeline, it could look like this:
- powershell: |
function Convert-ArmOutputToPsObject {
param (
[Parameter(Mandatory=$true)]
[string]
$ArmOutputString
)
if ($PSBoundParameters['Verbose']) {
Write-Host "Arm output json is:"
Write-Host $ArmOutputString
}
$armOutputObj = $ArmOutputString | ConvertFrom-Json
$armOutputObj.PSObject.Properties | ForEach-Object {
$type = ($_.value.type).ToLower()
$keyname = "ArmOutputs.$($_.name)"
$value = $_.value.value
if ($type -eq "securestring") {
Write-Host "##vso[task.setvariable variable=$keyname;issecret=true]$value"
Write-Host "Added Azure DevOps secret variable '$keyname' ('$type')"
} elseif ($type -eq "string") {
Write-Host "##vso[task.setvariable variable=$keyname]$value"
Write-Host "Added Azure DevOps variable '$keyname' ('$type') with value '$value'"
} else {
Throw "Type '$type' is not supported for '$keyname'"
}
}
}
Convert-ArmOutputToPsObject -ArmOutputString '$(ArmOutputs)' -Verbose
displayName: "Parsing outputs from ARM deployment to pipeline variables"
There is an extension called Arm Outputs. It works by querying the Azure Resource Manager API to see the last deployment and query the outputs from this API. Therefore, theoretically it’s possible if multiple pipelines deploy to the same resource group, there could be a race condition.