ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

clarify config block in terraform_remote_state 

This seems to be a common mistake - saw it in StackOverflow
and in several issues.
This commit is contained in:
Yuri Astrakhan 2019-06-20 21:11:28 +03:00 committed by Yuri Astrakhan
parent 56e33a4546
commit 0bd29ce194
1 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
website/upgrade-guides/0-12.html.markdown
View File

@ -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 of individual configurations in any order, without breaking
`terraform_remote_state` usage. `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 ### Attributes vs. blocks
Terraform resource configurations consist of both arguments that set Terraform resource configurations consist of both arguments that set