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:
parent
56e33a4546
commit
0bd29ce194
|
@ -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
|
||||
|
|
Loading…
Reference in New Issue