Azure-Templates | Azure Templates for Fortinet Solutions | Azure library

When you use a template in a pipeline, you are only consuming the .yml template file, not the entire repository that contains the template. So by default no other additional files (besides the template itself) that may exist in the template repository will be available when the primary pipeline is composed.

If you need access to scripts or other files that exist in your template repository you will need to use the checkout task and actually checkout the template repository.

- checkout: git://MyProject/MyTemplateRepo

One thing to be aware of if you go down the path of checking out multiple repositories is that it will cause the structure of your $(Build.SourcesDirectory) to change. In practice this can cause pain as you have to update any tasks that expected your primary repository location to be at the root of $(Build.SourcesDirectory).

That mutation of the $(Build.SourcesDirectory) might not be a big deal for you for new pipelines. It can turn into a pain if you have lots of pipelines that you want to consume a new template in, that require supporting scripts.

One option is to package the supporting template scripts, and publish them to an internal package feed. Then within your template block pull down the required script as a package. I have used this strategy before with templates that needed supporting powerShell scripts. We pipeline those scripts and publish them as a universal packages, then consume them at the template level.

You can consider to use build matrix which is one feature of YAML to achieve the test ran with multiple simulators:

According to your description, I assumed that you are deploying your WebApp with App Service Environment via Azure ARM template. Based on your template, I have tested it on my side and I could reproduce this issue.

I found a issue about creating an App Service Environment, and as Stefan Schackow who is the Principal Program Manager Lead of Azure Web Sites commented as follows:

Just in case anyone runs into this - we uncovered a bug where the App Service management infrastructure isn't correctly handling the normalized location string returned from the resourceGroup.Location() call. For now, the workaround is as mentioned above - grab the March 21st version of the templates and explicitly provide a string for "location" in the azuredeploy.parameters.json file.

For now, the workaround is that you need to explicitly provide a string for "location" in the azuredeploy.parameters.json file. I would report this issue, also you could add your feedback here.

According to the official document which you provided.

Ensure that the application is able to connect to each cluster node using its public or private IP address. To ensure connectivity, you have two options:

Host the application in the same network as the MongoDB cluster so that it can address each node using its private IP address. This is the recommended configuration for production environments. Host the application in a different network and assign public IP addresses, with appropriate firewall rules, to the cluster nodes (if not already assigned by default) so that the application can address each node using its public IP address. This configuration is not recommended for production environments.

So, if you test in the same Azure Virtual Network, you could use private IP(example 10.0.0.6). I test in my lab, I use python with this example.

If use the template that you mentioned, I also can repro the issue. If add the following code in the properties,it can create hostingEnvironment successfully. Please have a try with the following code

Well, you obviously want a string, not an object :)