tevert/vsts-release-terraform

VSTS Build/Release task for Terraform commands

vsts-release-terraform's Issues

Use API to determine available Terraform versions, not HTML scraping

See comment: hashicorp/terraform#9803 (comment)

In the spirit of Seth's comment, it might also make sense to change the Version field to a dropdown of major/minor versions. But then I'd need to be constantly adding new dropdown items....

Failure on Plan Stage

Running "Plan" causes failure. With leaving out a step for "init" prior to it generates a blank error.

When running "init" followed by "plan" you recieve the following error on the plan stage:

erraform version:
Terraform v0.11.1
+ provider.azurerm v0.3.3
+ provider.random v1.1.0
Running: terraform plan
�[0m�[1mRefreshing Terraform state in-memory prior to plan...�[0m'
The refreshed state will be used to calculate this plan, but will not be persisted to local or remote state storage.
�[0m
------------------------------------------------------------------------
�[31m
�[1m�[31mError: �[0m�[0m�[1mError running plan: 1 error(s) occurred:
* provider.azurerm: Azure CLI Authorization Profile was not found. Please ensure the Azure CLI is installed and then log-in with az login.�[0m
�[0m�[0m�[0m
Terraform failed to execute. Error:
End of Task Terraform

Passing Variables

Do you have any examples on how to pass the variables? I have the variables defined in the library and linked to the build job but they seem to not be referencing. I added the following line to attempt to call them:

-var 'subscription_id=vars' -var 'client_id=vars' -var 'client_secret=vars' -var 'tenant_id=vars'

and flipped it around as well to:

-var 'vars=subscription_id' -var 'vars=client_id' -var 'vars=client_secret' -var 'vars=tenant_id'

My code I have tried using

variable subscription_id {
description = "words in here"
}

as well as:

provider "azurerm" {
subscription_id = "${var.subscription_id}"
client_id = "${var.client_id}"
client_secret = "${var.client_secret}"
tenant_id = "${var.tenant_id}"
}

but cannot seem to get the variables to take. Get an error telling me:

- provider config 'azurerm': unknown variable referenced: 'subscription_id'; define it with a 'variable' block
- provider config 'azurerm': unknown variable referenced: 'client_id'; define it with a 'variable' block
- provider config 'azurerm': unknown variable referenced: 'client_secret'; define it with a 'variable' block
- provider config 'azurerm': unknown variable referenced: 'tenant_id'; define it with a 'variable' block

Each time I run it.

Add other types of remote state storage?

Or maybe the better approach is just to force people to define their remote state as part of the templates themselves. Needs a bit of investigation.

Add ability to set TF_LOG

I'm new the the VSTS deployment process but pretty good with PowerShell. It should be pretty easy to add by implementing a picklist with the different TF_LOG options defaulting to ERROR and then adding something like this to the invoke-terraform:

$tf_log = Get-VstsInput -Name tf_log
[Environment]::SetEnvironmentVariable("TF_LOG", $tf_log, "Process")

I would do this myself, but I am not entirely sure how to go about it.