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

fix: tighten behavior description

This commit is contained in:
GoodmanBen 2022-03-10 19:01:58 -05:00
parent 32d9aa0ffd
commit 478b4e0aea
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
website/docs/language/files/override.mdx
View File

@ -152,6 +152,6 @@ original block. If both the base block and the override block both set
`required_version` then the constraints in the base block are entirely ignored.
If a `cloud` block is set within the original configuration's `terraform` block and a `backend` block
is set in the override file, then the backend specified by the `backend` block is used upon merging.
is set in the override file, then the backend specified by the `backend` block is used by Terraform upon merging.
Similarly, if a `backend` block is set within the original configuration's `terraform` block
and a `cloud` block is set in the override file, then the backend specified by the `backend` block is used upon merging.
and a `cloud` block is set in the override file, then the backend specified by the `backend` block is used by Terraform upon merging.

2
website/docs/language/settings/terraform-cloud.mdx
View File

@ -30,6 +30,6 @@ terraform {
You cannot use the CLI integration and a [state backend](/language/settings/backends) in the same configuration; they are mutually exclusive.
A configuration can only provide one `cloud` block and the `cloud` block cannot refer to named values like input variables, locals, or data source attributes.
Note that a `cloud` block can be overridden by a state backend in an [override file](/language/files/override#merging-terraform-blocks).
Note, however, that a `cloud` block can be overridden by a state backend in an [override file](/language/files/override).
Refer to [Using Terraform Cloud](/cli/cloud) in the Terraform CLI docs for more information.