This contains the Azure Devops Pipeline tasks for installing and executing terraform commands within a build or release. These tasks are intended to work on any build agent. They are also intended to provide a guided abstraction to deploying infrastructure within Azure.

This repo provides two tasks

• Terraform Installer - Responsible for installing terraform on a build agent
• Terraform CLI - Responsible for executing the terraform cli commands.

See readme for each of the tasks for development setup for each.

Add support for secure .env files. Secure variable files chosen that end in .env will be treated as .env files. The environment variables within the file will be emitted to the task process so that they are available to terraform.

Fixed issue where backend storage account creation would return error due to deprecated storage account kind. This was due to a change in azure storage.

Fixed issue where task would fail when using TF_LOG debug variable. When this variable was used, logging would be written to stderr even when the command was successful (i.e. exit code 0). This would cause the task to decide the command failed due to the existence of content in stderr. The fix changes the decision to be based of the exit code. This should allow for TF_LOG to be used and the task succeed when the underlying command succeeds.

Parse errors from stderr output and write to exception telemetry.

Record which command option flags were used during execution without values in telemetry.

This change will introduce two new pipeline variables that will be available to subsequent tasks in response to #68

The first is available after any terraform command used and is TERRAFORM_LAST_EXITCODE. This will contain the exit code emitted from the terraform executable when the task was run.

The second is available only for terraform plan and is TERRAFORM_PLAN_HAS_CHANGES. This will have either true or false as valid values and will indicate true if plan detected changes. If -detailed-exitcode is not provided in command options, this variable will always be true. However, if -detailed-exitcode is provided, then this variable will be set to false if exit code 0 (empty diff) was emitted.

As reported in #16, the -detailed-exitcode option would produce exit code 2 if changes were detected. The azure-pipelines-task-lib library would interpret this as a failure. Now if the -detailed-exitcode option is provided, exit code 2 will be considered a successful execution.

Fixed issue where errors where occurring for storage accounts that were not of kind "BlobStorage". The underlying azure cli storage account create command was being executed regardless of the storage account's existance. If the storage account existed prior to executing the command, the command would attempt to set the storage account to kind "BlobStorage" access tier "hot" and configured sku. This would result in an error when updating storage account to this configuration was not supported. Example would be updating existing storage accounts that are kind "StorageV2" to "BlobStorage". This update is not permitted.

With this change, no attempt will be made to update existing storage accounts.

Fixed issue where automatically injected apply command options -auto-approve and -var-file were being placed after output plan file path. Output file plan path was being provided in the Command Options input field. The auto injected options would be appended after the user provided options. The auto injected options will now be inserted ahead of user provided options. This will allow users to provide a plan path at the end of their provided options to ensure all options are ordered as terraform expects.

Fixed validation error reported during marketplace upload documented with issue #35.

#19 Create/Ensure AzureRM Backend Storage Account

The task supports automatically creating the resource group, storage account, and container for remote azurerm backend. To enable this, select the task for the terraform init command. Check the checkbox labeled "Create Backend (If not exists)" underneath the backend type drop down. Once selected, the resource group location and storage account sku can be provided. The defaults are 'eastus' and 'Standard_RAGRS' respectively. The task will utilize AzureCLI to create the resource group, storage account, and container as specified in the backend configuration.

• #22 Updated the overview docs to include references to destroy command support
• #32 Updated the default version of the installer to be the latest version of terraform

• Added support for terraform destroy command #22 and PR #31
• Updated readme and sample env #23 and PR #24

Duplicated working directory input parameter was removed #17

The task now supports the ability to upload and use a variable file that contains secrets. This stores the files using the Secure Files feature in Azure DevOps. The files are downloaded to a temporary location on the build agent while running a build or release. The file is removed from the agent after the build or release completes.

A new input has been added Command Options that will allow for defining command options that do not otherwise have dedicated inputs. For example, the following value could be provided in the command options field when running validate

-input=true -lock=false -no-color

This would result in the task executing validate as follows

terraform validate -input=true -lock=false -no-color

Command options will always precede any other options that are generated via dedicated input such as backend config and/or variable file.

This error was due to a packaging issue with the vsix that was introduced with the changes to shrink the vsix. The changes for the shrink has been reworked to ensure runtime dependencies are included with the vsix package.

Implemented new scripts for selecting only files required for task execution to be included in vsix. See #8 VSIX Size Too Large for Marketplace Upload