Azure ARM Template Design

Operations

buildARMTemplate

Input

• Template/parameter files can directly reside under Git repo or can be present under any subfolder. There could be one/multiple Template/parameter files present in same Git repo.

• However related template json & parameter json must be under same folder.

• Parameter files can contain dynamic placeholder(e.g. ${{Change_Runtime_Prop}}). They can be replaced during execution through project/environment properties.

• In case of nested template file, all files should be kept under same folder(or sub folder), but the main template file name should be provided as input.

• In case of multiple template files in the directory, provide the exact template file name. In case wild card value the result should return one template file only.

• In case of multiple parameter file in the directory, provide the exact parameter file name In case wild card value the result should return one parameter file only.

• In case single template/parameter file inside directory no file name info is needed. Plugin will filter the files automatically.

• Template file should have the word “Template” in its naming convention. Naming convention required for auto-populate template file details(just above use-case). The naming convention is also required for some internal purpose.

• Parameter file should have the word “Parameter” in its naming convention with same purpose as mentioned above.

• Wild card file names can also be provided , e.g. VM_Param* or *storage*.json . However this must return individual file only.

• In case multiple template/parameter file inside directory and no information provided, flow shall fail.

• It will keep other template files in the artifact folder as well, in case there is nested template.

• All relevant template/parameter file will be moved to Artifact folder.

• In case Pass values during execution use case with no Parameter file available(refer to executeARMTemplateGroup), Parameter file name should be given as “NA”

• This flow will also create a manifest.json file. It will contain the main template & parameter file mapping in json format(required during deployment). e.g.

[{

"templateFile": "VMTemplate/vmCreationTemplate.json",

"paramFile": " VMTemplate/parameter.json"

}

or

{

"templateFile": "VMTemplate/vmCreationTemplate.json",

"paramFile": " NA"

}]

In case one may want to deploy multiple templates together, same can be achieved as well. All values should be passed as comma separated.

[

{

"templateFile":"Path1/Template1.json",

"paramFile":"Path1/ParamFile1.json"

},

{

"templateFile":"Path2/Template2.json",

"paramFile":"NA"

},

{

"templateFile":"Path3/Template3.json",

"paramFile":"Path3/Param_storage.json"

}

]

n.b. user should be careful while providing the data. Any missing value/incorrect sequence of file may lead to unexpected result/error.

This operation will have the option to create artifact.

Output

executeARMTemplate

Inputs

Properties

• As part of artifact relevant template & parameter files will exist.

• The manifest file should also provide details on template & parameter file

• This operation will read the template details from manifest.json and execute.

• All the parameter arguments which are env-specific should be configured as Project/environment variables and should be configured in topology with proper values.

• Parameter values can also be passed as input argument.

• The input Parameter values can be passed as below highlighted format.

az group deployment create -g MyResourceGroup --template-file azuredeploy.json \

--parameters "{ \"location\": { \"value\": \"westus\" } }"

az group deployment create -g MyResourceGroup --template-file azuredeploy.json \

--parameters @params.json --parameters https://mysite/params.json --parameters DBMasterUserPassword=${DBMasterUserPassword}

• In case both parameter file is passed and dynamic parameter values is provided both of them will be considered. The flow will use both input parameters & parameter file content(with input param takin precedence).

• This will also replace all env specific values in parameter file(s).

• Missing parameter validation – This is a list value with possible options- Fail / Remove

Options Fail: All actual values corresponding to the arguments present in the parameter file must be provided. In case of any value not provided by user/env variables, the flow shall fail.

Option Remove(default): The plugin should remove the parameters for which values are not provided. The template would try to execute with the default values. But the execution would proceed. In case mandatory field missing deployment shall fail.

Output

Execution steps