I am confused about where to use a variable and where to use a parameter in ARM templates. How do we make this call ?
The referenced script uses both. I am more curious of the justification of using variables.
Reference
Sample Service Fabric Azure Deploy Script
https://raw.githubusercontent.com/azure/azure-quickstart-templates/master/service-fabric-oms/azuredeploy.json
Parameters allow you to pass different values to the ARM template for use during the deployment. Some common examples include names of resources or which Azure region to host them. Parameters enable your templates to be more dynamic and used across different environments.
Parameters are external values passed into pipelines. They can't be changed inside a pipeline. Variables, on the other hand, are internal values that live inside a pipeline. They can be changed inside that pipeline.
You're limited to 256 parameters in a template. You can reduce the number of parameters by using objects that contain multiple properties. Name of the parameter.
The default value attribute is used to make a parameter optional: if you deploy the template and don't specify a value for a particular parameter, ARM will just use the default value configured on that parameter. If you don't specify a value and the parameter doesn't have a default value, you get a deployment error.
In the Azure template json file:
parameters:Values that are provided when deployment is executed to customize resource deployment.
variables:Values that are used as JSON fragments in the template to simplify template language expressions.
More information please refer to this official document:Understand the structure and syntax of Azure Resource Manager templates.
I am more curious of the justification of using variables.
Based on my experience, if you only use the variable once, you don't need use variables. But if you want to use the variable multiple times, you had better use variables. Using variable can simplify your template to avoid duplication of content.
For example, if you don't use supportLogStorageAccountName more than once, you can just do:
"name": "[toLower(concat('sf', uniqueString(resourceGroup().id),'2'))]"
However if you use provide variable supportLogStorageAccountName several\many times, you can use variable to avoid duplication.
ARM templates are usually used to create a set of close to identical environments. The parameters are what differs them. This is commonly used for environment type (prod, dev, test) and performance/cost related parameters. Variables are used to create unique names for services based on or calculated from the parameters.
An example of this would the name of a storage account. This is usually done by concatenating a common name like _storage and an environment name parameter like “test” and store it in a variable. When you create another environment all you must do is change the environment type parameter.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With