Accept maps as provider blocks

[moio]

Terraform Version

Latest 0.7.7

Affected Resource(s)

Core.

Terraform Configuration Files

Example on AWS:

resource "aws_instance" "web" {
   ...
   ebs_block_device = "${var.device}"
}

Expected Behavior

Assuming ${var.device} is a map with keys corresponding to the expected keys, the definition is equivalent to an inline one.

Actual Behavior

Type error: got map while expecting object.

Steps to Reproduce

terraform plan

Important Factoids

This first came up while developing a libvirt provider, where we do not have an equivalent of the volume_attachment resources.

Question is: should such a resource really be added to the provider, or is this a core Terraform issue that will eventually be solved at language level?

[apparentlymart]

Hi @moio! Sorry for the long silence here.

I think this issue is covering the same use-cases as #7034, which has now been closed due to a new feature merged into master for inclusion in the forthcoming v0.12.0 release. I've left a comment over there illustrating how it works.

Thanks for requesting this, and sorry we didn't catch it on earlier updates.

[moio]

Hey @apparentlymart! This is actually fantastic news and I can't wait to jump on v0.12 to enjoy all the new constructs and facilities.

Please accept my personal thanks and feel free to relay them to the whole team too - we know very well that sometimes it's best to wait for the right architectural solution to solve a broad range of issues instead of just adding hacks here and there and ending up with an unmaintanable mess.

Best of luck for v0.12!

[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.