ARM Outputs

This extension enables you to use the ARM Deployment outputs in your VSTS environment.

This step will use the last successful deployment within the selected resource group. If this deployent has outputs, all of them are copied to VSTS variables by the ARM Output key.

This outputs can then be used by default VSTS ways: $(same-key-as-in-arm-template)

Usually this task is ran directly after the 'Azure Resource Group Deployment' task.

Release notes

Version 4.0 - 02-09-2018

• Support for complex outputs
• Now based on AzurePowershell task handler
  • Improved performance
  • Less dependencies
  • Easier to port to Linux agents Powershell Core on VSTS becomes a thing

Version 3.0 - 01-02-2018

• Filter on deployment name

Version 2.0 - 18-11-2017

• LastDeploymentBehaviour added

Version 1.0 - 13-04-2017

• LastDeploymentBehaviour added

Parameter usage

Secrets

If your output is of type SecureString the output value cannot be read and these outputs are therefore ignored.

You can off course output your secrets as string but then these values might be exposed in logfiles (and visible via the Azure Portal as well)

Prefix

Using the 'prefix' parameter, it is possible to prefix the variables used within VSTS. A prefix can be used to distinct variables coming out of ARM from regular VSTS variables. A prefix can also be to prevent collisions between ARM Output names and VSTS Variable names.

Output Names

Using the 'Output Names' parameter, it is possible to process only a subset of the ARM Outputs. When this field is left empty (it is by default) all ARM Outputs are used.

When last deployment is failed

Using the 'When last deployment is failed' parameter, you can choose the behaviour when the last deployment to a resource group has failed. There are two options, 1. fail the task (the default) or 2. take the last succesful deployment.

Filter deployment name

Optional string to filter deployments by. This can be useful if you have concurrent deployments to the same resource group. Deployment names in VSTS are the name of the json file plus date and time, so a file CreateKeyVault.json could have a deployment name of CreateKeyVault-20180025-151538-0688. In this case, if you want to filter to deployments of this file enter CreateKeyVault as the filter

Complex outputs

If your output is not a single value but a complex type, like:

{
   "someKey":"someValue",
   "second":{
      "foo":"bar",
      "oops":{
         "asdasdasd":true,
         "array":[
            {
               "asd":"qqq"
            },
            {
               "efg":"aaa"
            }
         ]
      }
   }
}

This will result in the following 5 variables:

complex.second.foo => bar
complex.second.oops.array[0].asd => qqq
complex.second.oops.array[1].efg => aaa
complex.second.oops.asdasdasd => True
complex.someKey => someValue

Help & Contact

Find me at http://case.schollaart.net/. Experiencing problems, or do you have an idea? Please let me know via Twitter or by mail. Or even better, raise an issue on GitHub.