Implementing Azure DevOps Solutions

Parameters

Every template has to start with a parameters section. This section takes the shape of a JSON object, which can be empty but cannot be left out. The use of this section is to declare one or more parameters that can be specified by the caller of the ARM template, before deploying it. A common reason for using the parameters section is to use the same template for both the test and production environment, but varying the names of resources between the two. An example parameters section might look like this:

{  “appServiceName”: {    “type”: “string”,    “metadata”: {      “description”: “a free to choose text”    }}

For every parameter, a new key is specified with the parameter's name. The value is an object. This object has one mandatory key, ...