Reputation: 331
Is there any way to use conditional statements in templates?
for example I am building template which will have vms with data disks on QA and Production, but no data disks on Dev. Another scenario would be there are some extensions only needs to be installed in prod VMs but no where else.
Any help is appreciated.
Upvotes: 8
Views: 9518
Reputation: 291
You can leverage the newly released comparison functions to accomplish most of this.
Here is an example of how you would use a parameter to determine if a storage account should be deployed.
Parameter:
"deployStorage": {
"type": "string"
},
Resource:
{
"condition": "[equals(parameters('deployStorage'),'yes')]",
"name": "[variables('storageAccountName')]",
"type": "Microsoft.Storage/storageAccounts",
"location": "[resourceGroup().location]",
"apiVersion": "2017-06-01",
"sku": {
"name": "[parameters('storageAccountType')]"
},
"kind": "Storage"
}
Notice the new condition property in the resource along with the most recent API version for the storage provider.
Upvotes: 10
Reputation: 804
The key properties to achieve this are:
templateLink
that sets the template to be included and the names of the parameters to be passed to the called template.
"templateLink": {
"uri": "[variables('sharedTemplateUrl')]",
"contentVersion": "1.0.0.0"
}
newOrExisting
based on its value we can decide to use an QA versus Productoin config.
"newOrExisting": "new",
"configHash": {
"new": "[concat(parameters('templateBaseUrl'),'partials/QA.json')]",
"existing": "[concat(parameters('templateBaseUrl'),'partials/Production.json')]"
}
"configTemplate": "[variables('configHash')[parameters('Settings').newOrExisting]]"
You could see Azure ARM deployments: how to perform conditional deployments which has provided more details.
Upvotes: 4