{"id":11,"date":"2017-04-05T15:00:21","date_gmt":"2017-04-05T21:00:21","guid":{"rendered":"http:\/\/peterod.azurewebsites.net\/?p=11"},"modified":"2017-04-05T15:00:21","modified_gmt":"2017-04-05T21:00:21","slug":"programmatically-adding-elements-to-an-azure-arm-template-using-powershell","status":"publish","type":"post","link":"http:\/\/www.perktime.org\/index.php\/2017\/04\/05\/programmatically-adding-elements-to-an-azure-arm-template-using-powershell\/","title":{"rendered":"Programmatically adding elements to an Azure ARM template using PowerShell"},"content":{"rendered":"

One of the great features of Azure ARM templates is that you can do template linking so that you can split your deployment into smaller components. This promotes better reuse as well as less unwieldy template files. However, one limitation today is that it is not easily possible to do conditional logic within your ARM template (see this blob post for one possible method using arrays: <\/span>https:\/\/jodygblog.wordpress.com\/2016\/05\/02\/conditional-parameters-for-arm-templates\/<\/span><\/a>). However, this technique does not work in all situations. For example, if you wanted a base Windows\/Linux template and wanted to have one base template that utilizes an availability set and one that did not, you would need to create two versions of the base template. This is definitely not ideal because now you have to make changes to two base templates instead of one. <\/span>
\nA solution to this is to use PowerShell\u2019s ability to load a JSON file, make changes as required in memory and then emit the JSON file back to disk. You still have two base template files but only one of them will need to be edited manually and the other will be a generated file. <\/span>
\nUsing our example of having two base Windows templates with and without an availability set, this section demonstrates how the additional JSON can be added using PowerShell. We would first need to have variables for the additional JSON for elements like parameters, resources, and properties:<\/span>
\nparam
\n(
\n[string]$InputJsonFilePath,
\n[string]$OutputJsonFilePath,
\n[bool]$IsManagedAvailabilitySet #if this is a managed availability set, set this to true otherwise false<\/span>
\n)<\/span>
\n$availabilitySetParam =@”
\n{
\n“type”:”string”,
\n“metadata”:
\n{
\n“description”: “Name of the availability set”
\n}
\n}
\n“@
\n$faultDomainParam = @”
\n{
\n“type”: “int”,
\n“defaultValue”: 3,
\n“metadata”: {
\n“description”: “Fault Domain Count”
\n}
\n}
\n“@
\n$updateDomainParam = @”
\n{
\n“type”: “int”,
\n“defaultValue”: 5,
\n“metadata”: {
\n“description”: “Update Domain Count”
\n}
\n}
\n“@<\/span>
\n$availabilitySetResourceJson = @”
\n{
\n“type”: “Microsoft.Compute\/availabilitySets”,
\n“name”: “[parameters(‘availabilitySetName’)]”,
\n“apiVersion”: “2016-04-30-preview”,
\n“location”: “[resourceGroup().location]”,
\n“tags”: {
\n“displayName”: “Availability Set”
\n},
\n“properties”: {
\n“platformFaultDomainCount”: “[parameters(‘faultDomainCount’)]”,
\n“platformUpdateDomainCount”: “[parameters(‘updateDomainCount’)]”,
\n“managed”: false
\n}
\n}
\n“@<\/span>
\n$availabilitySetVMPropertiesJson = @”
\n{
\n“id”: “[resourceId(‘Microsoft.Compute\/availabilitySets’ , parameters(‘availabilitySetName’))]”
\n}
\n“@<\/span>
\n 
\nNext we would load our JSON file into memory and convert each of the JSON variables into JSON objects:<\/span>
\n 
\n$JsonFile = Get-Content $InputJsonFilePath |Out-String
\n$JsonFile = ConvertFrom-Json $JsonFile<\/span>
\n$availabilitySet = ConvertFrom-Json -InputObject $availabilitySetParam
\n$faultDomain = ConvertFrom-Json -InputObject $faultDomainParam
\n$updateDomain = ConvertFrom-Json -InputObject $updateDomainParam
\n$availabilitySetResource = ConvertFrom-Json -InputObject $availabilitySetResourceJson
\n$availabilitySetProperty = ConvertFrom-Json -InputObject $availabilitySetVMPropertiesJson<\/span>
\n 
\nNow this is where the real magic happens. \"Smile\" We use Add-Member<\/strong> to add the new parameters:<\/span>
\n 
\n$JsonFile.parameters |Add-Member -Name “availabilitySetName” -MemberType NoteProperty -Value $availabilitySet
\n$JsonFile.parameters |Add-Member -Name “faultDomainCount” -MemberType NoteProperty -Value $faultDomain
\n$JsonFile.parameters |Add-Member -Name “updateDomainCount” -MemberType NoteProperty -Value $updateDomain<\/span>
\n 
\nFor elements in the JSON file that are arrays, we use \u2018+\u2019 to add an element to the array:<\/span>
\n$JsonFile.resources = $JsonFile.Resources + $availabilitySetResource<\/span>
\n 
\nWe now add a \u201cDependsOn\u201d as well as an AvailabilitySet property:<\/span>
\nforeach ($vm in $JsonFile.Resources)
\n{
\nif ($vm.type -eq ‘Microsoft.Compute\/virtualMachines’)
\n{
\n$vm.dependsOn = $vm.dependsOn + “[resourceId(‘Microsoft.Compute\/availabilitySets’, parameters(‘availabilitySetName’))]”
\n$vm.properties |Add-Member -Name “availabilitySet” -MemberType NoteProperty -Value $availabilitySetProperty
\n}<\/span>
\n\u00a0\u00a0\u00a0 if ($vm.type -eq ‘Microsoft.Compute\/availabilitySets’)
\n{
\nif ($IsManagedAvailabilitySet)
\n{
\n$vm.properties.managed = $true
\n}
\nelse
\n{
\n$vm.properties.managed = $false
\n}
\n}
\n}<\/span>
\nLastly we write the JSON file back to disk. Note that by default ConvertTo-JSON has a depth of 2 which will likely not be sufficient. Also, it will escape characters by default. <\/span>
\nConvertTo-Json -Depth 10 -InputObject $JsonFile |Out-File $OutputJsonFilePath \u2013Force<\/span>
\nTo remove the escape characters (which is purely for readability), you can reload the file and do a string replacement:<\/span>
\n 
\n$jsonFile = $jsonFile.Replace(‘\\u0027’, “‘”)
\n$jsonFile |Out-File -FilePath $OutputJsonFilePath -force<\/span>
\n 
\nWell, that\u2019s all there is to it. You could use this same technique in other ways such as having base template with or without managed disks, copying parameters to multiple files, etc. <\/span>
\n 
\nUpdated: Corrected API version in availability set resource JSON to 2016-04-30-preview. <\/strong><\/span>
\n 
\n 
\nHere is the complete PowerShell for your convenience:<\/span>
\nparam
\n(
\n[string]$InputJsonFilePath,
\n[string]$OutputJsonFilePath,
\n[bool]$IsManagedAvailabilitySet #if this is a managed availability set, set this to true otherwise false<\/span>
\n)
\n$availabilitySetParam =@”
\n{
\n“type”:”string”,
\n“metadata”:
\n{
\n“description”: “Name of the availability set”
\n}
\n}
\n“@
\n$faultDomainParam = @”
\n{
\n“type”: “int”,
\n“defaultValue”: 3,
\n“metadata”: {
\n“description”: “Fault Domain Count”
\n}
\n}
\n“@
\n$updateDomainParam = @”
\n{
\n“type”: “int”,
\n“defaultValue”: 5,
\n“metadata”: {
\n“description”: “Update Domain Count”
\n}
\n}
\n“@<\/span>
\n$availabilitySetResourceJson = @”
\n{
\n“type”: “Microsoft.Compute\/availabilitySets”,
\n“name”: “[parameters(‘availabilitySetName’)]”,
\n“apiVersion”: “2016-04-30-preview”,
\n“location”: “[resourceGroup().location]”,
\n“tags”: {
\n“displayName”: “Availability Set”
\n},
\n“properties”: {
\n“platformFaultDomainCount”: “[parameters(‘faultDomainCount’)]”,
\n“platformUpdateDomainCount”: “[parameters(‘updateDomainCount’)]”,
\n“managed”: false
\n}
\n}
\n“@<\/span>
\n$availabilitySetVMPropertiesJson = @”
\n{
\n“id”: “[resourceId(‘Microsoft.Compute\/availabilitySets’ , parameters(‘availabilitySetName’))]”
\n}
\n“@<\/span>
\n$JsonFile = Get-Content $InputJsonFilePath |Out-String
\n$JsonFile = ConvertFrom-Json $JsonFile<\/span>
\n$availabilitySet = ConvertFrom-Json -InputObject $availabilitySetParam
\n$faultDomain = ConvertFrom-Json -InputObject $faultDomainParam
\n$updateDomain = ConvertFrom-Json -InputObject $updateDomainParam
\n$availabilitySetResource = ConvertFrom-Json -InputObject $availabilitySetResourceJson
\n$availabilitySetProperty = ConvertFrom-Json -InputObject $availabilitySetVMPropertiesJson<\/span>
\n$JsonFile.parameters |Add-Member -Name “availabilitySetName” -MemberType NoteProperty -Value $availabilitySet
\n$JsonFile.parameters |Add-Member -Name “faultDomainCount” -MemberType NoteProperty -Value $faultDomain
\n$JsonFile.parameters |Add-Member -Name “updateDomainCount” -MemberType NoteProperty -Value $updateDomain
\n$JsonFile.resources = $JsonFile.Resources + $availabilitySetResource<\/span>
\nforeach ($vm in $JsonFile.Resources)
\n{
\nif ($vm.type -eq ‘Microsoft.Compute\/virtualMachines’)
\n{
\n$vm.dependsOn = $vm.dependsOn + “[resourceId(‘Microsoft.Compute\/availabilitySets’, parameters(‘availabilitySetName’))]”
\n$vm.properties |Add-Member -Name “availabilitySet” -MemberType NoteProperty -Value $availabilitySetProperty
\n}<\/span>
\n\u00a0\u00a0\u00a0 if ($vm.type -eq ‘Microsoft.Compute\/availabilitySets’)
\n{
\nif ($IsManagedAvailabilitySet)
\n{
\n$vm.properties.managed = true
\n}
\nelse
\n{
\n$vm.properties.managed = false
\n}
\n}
\n}<\/span>
\nConvertTo-Json -Depth 10 -InputObject $JsonFile |Out-File $OutputJsonFilePath -Force\u00a0 <\/span>
\n$JsonFile = Get-Content $OutputJsonFilePath |Out-String
\n$jsonFile = $jsonFile.Replace(‘\\u0027’, “‘”)
\n$jsonFile |Out-File -FilePath $OutputJsonFilePath -force<\/span>
\n <\/p>\n","protected":false},"excerpt":{"rendered":"

One of the great features of Azure ARM templates is that you can do template linking so that you can split your deployment into smaller components. This promotes better reuse as well as less unwieldy template files. However, one limitation today is that it is not easily possible to do conditional logic within your ARM … <\/p>\n

Continue reading “Programmatically adding elements to an Azure ARM template using PowerShell”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-11","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/posts\/11","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/comments?post=11"}],"version-history":[{"count":1,"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/posts\/11\/revisions"}],"predecessor-version":[{"id":23,"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/posts\/11\/revisions\/23"}],"wp:attachment":[{"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/media?parent=11"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/categories?post=11"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.perktime.org\/index.php\/wp-json\/wp\/v2\/tags?post=11"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}