azurerm_template_deployment fails to pass "array" type parameters properly

[rtyler]

Terraform Version

v0.8.0

Affected Resource(s)

• azurerm_template_deployment

Terraform Configuration Files

Consider the an ARM template with an "array" parameter, e.g.:

{
    "$schema": "http://schemas.management.azure.com/schemas/2015-01-01/deploymentTemplate.json#",
    "contentVersion": "1.0.0.0",
    "parameters": {
        "documentDBs": {
            "type": "array"
        }
    },

resource "azurerm_template_deployment" "thing" {
    name                = "a-big-parameterized-arm-template"
    resource_group_name = "${azurerm_resource_group.things.name}"
    parameters          = {
        documentDBs = [
            "github-events",
        ],
    }
    deployment_mode     = "Incremental"
    template_body       = "${file("./arm_templates/the-template.json")}"
}

Output

Error running plan: 1 error(s) occurred:

* parameters: 1 error(s) decoding:

* '[documentDBs]' expected type 'string', got unconvertible type '[]interface {}'

Expected Behavior

I would have expected the array to be marshalled through to the template properly.
What should have happened?

[pearcec]

Any possible workarounds? I am working on automating the Protection of a VM. Perhaps taking a string value from terraform and creating an array with it inside json?

[phekmat]

Perhaps taking a string value from terraform and creating an array with it inside json?

I'm using vars with template_files in a few places to generate the ARM template with the array/object values baked in. Unfortunately, this doesn't work for more complex scenarios like referencing a Key Vault secret, since that has to be in the parameters file instead of the main template.

[jkalwar]

I have a similar issue , unable to pass arrays as parameters in azurerm_template_deployment , do we have a solution for this issue ?

[aykay76]

We also have a requirement for this.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.