AzureDeploy | ARM templates for Azure | Azure library

This behavior seems to be poorly documented, but from the documentation page for the Windows custom script extension:

The name of the resource has to be in the format virtualMachineName/extensionName, if this extension is used as a standalone resource in the Azure Resource Manager template.

Which seems to imply that the resolution for where the custom script extension should be executed is based on the name. I imagine this is the case for Linux VMs too.

For the particular example that you are looking at, the name of one of the vms is:

You could specify 'only files in folders named X' with Where-Object on the Directory property:

Thank you Brian Moore. Posting your suggestion as an answer to help other community members.

this is because anything that is not the "main template" is assumed to be a nested template... main template is determined by the filename (unless you specify otherwise).

I think short term you'll have to follow the pattern - until we have a more standard way of determining name / nested.

You can refer to "Location Should Not Be Hardcoded" test catching errors in good templates

You need to extract the autoscalesettings into a dedicated variable and conditionally include that in the template depending on your parameters.

Full example: https://mattfrear.com/2020/06/17/conditionally-specify-a-property-in-an-arm-template/

Rough sketch on how this could look like (probably contains some small errors).

You can find the relevant documentation in the ManagedClusterProperties object

The trick here is to get the resource name and you can find the relevant documentation from the ARM documentation by mapping the reosurce

I have an example here that I built decompiling the arm template sample you showed into bicep.

https://github.com/markjbrown/azure-quickstart-templates/tree/sql-sp/quickstarts/microsoft.documentdb/cosmosdb-sql-container-sprocs

I have not yet had a chance to complete the PR I have on this updated sample but this will get published where the ARM template you pointed to lives. But if you need an example that works to unblock you this is what you need.

UPDATE: Apologies for the empty bicep file. Not sure how that happened.

To get an example of how to deploy a UDF using bicep you can take the ARM template located here and then pass it to bicep's decompile function. Example below.

There are some mistakes in your ARM template such as the value of WORDPRESS_DB_HOST should be "127.0.0.1:3306" instead of "127.0.0.0:3306" and the port number should be "port": 3306 instead of "port": "3306". Also, the image wordpress does not work for me, instead, using the image wordpress:4.9-apache works.

Sample

You can use the function reference() to get the output in the link template:

You just need to add another stage with some conditions for the deployment to Test environment.

Normally, you can set up a multi-stage pipeline that contains the main processes for your application, such as "Build", "Test" and "Deploy". And like release pipeline, you also can set a stage for each deployment environment in the same pipeline.

In your case, if you want that when new changes occur on the UAT branch, the deployment to Test environment can be triggered, you can set the condition like as below on the stage for Test environment.