fix: tighten behavior description
This commit is contained in:
parent
32d9aa0ffd
commit
478b4e0aea
|
@ -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.
|
||||
|
|
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue