From 0bd29ce19450ffa2451071949ee2e2a05155adc3 Mon Sep 17 00:00:00 2001 From: Yuri Astrakhan Date: Thu, 20 Jun 2019 21:11:28 +0300 Subject: [PATCH] clarify config block in terraform_remote_state This seems to be a common mistake - saw it in StackOverflow and in several issues. --- website/upgrade-guides/0-12.html.markdown | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/website/upgrade-guides/0-12.html.markdown b/website/upgrade-guides/0-12.html.markdown index 8649d2657..b4025bd59 100644 --- a/website/upgrade-guides/0-12.html.markdown +++ b/website/upgrade-guides/0-12.html.markdown @@ -248,6 +248,17 @@ configurations to Terraform v0.11.14 first you can then perform v0.12 upgrades of individual configurations in any order, without breaking `terraform_remote_state` usage. +Note that the `config` block should now be in the form of an assignment with the `=` sign: + +```hcl +data "terraform_remote_state" "default" { + backend = "gcs" + config = { + bucket = "..." + } +} +``` + ### Attributes vs. blocks Terraform resource configurations consist of both arguments that set