Outputted map does not contain all expected keys

[moio]

Terraform Version

Latest 0.7.8

Affected Resource(s)

Core issue. Reproduced with either:

• aws_instance
• libvirt_volume and libvirt_domain

Terraform Configuration Files

• https://github.com/moio/terraform_output_map_issue_example

Please add proper AWS credentials in https://github.com/moio/terraform_output_map_issue_example/blob/master/main.tf#L2

Debug Output

https://gist.github.com/moio/2a980e348bccde29be8d13e47821e218

Expected Behavior

terraform_output_map_issue_example$ terraform plan
Refreshing Terraform state in-memory prior to plan...
...
+ module.base.aws_instance.example
...
+ module.extension.aws_instance.example

Plan: 2 to add, 0 to change, 0 to destroy

Actual Behavior

terraform_output_map_issue_example$ terraform plan
There are warnings and/or errors related to your configuration. Please
fix these before continuing.

Errors:

  * key "base_instance_id" does not exist in map var.configuration in:

Extension of ${var.configuration["base_instance_id"]}

Steps to Reproduce

• clone repo above
• add AWS credentials
• terraform plan

Important Factoids

I am trying to use a variable from an output of a module in another module.

Note that this does work in case of literals (param1 in the sample).

Also note that this does work using the hacky interpolated map literal syntax.

References

• outputting maps not working #8384
• Get rid of the list when parsing HCL maps for vars #9268

[flypenguin]

this is a major blocker in my current efforts to automate our whole vpc setup and I went pretty much crazy debugging my system until I found this. any ideas of when this is fixed?

[flypenguin]

BTW #6524 is also applicable to this - the map contents get indented every time I (in that case my editor) uses fmt before saving. pretty annoying :)

[mitchellh]

Fixed in master!

[moio]

Thanks everybody, great job!

[moio]

@mitchellh, @jbardin: JFYI while testing this I found several possibly related failures reported in #10187. Thanks again!

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