Merge pull request #1 from dragondrop-cloud/feature/update_override_documentation

Update documentation around `cloud` and `backend` override behavior
This commit is contained in:
GoodmanBen 2022-03-10 19:05:30 -05:00 committed by GitHub
commit b1532c4318
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 1 deletions

View File

@ -150,3 +150,8 @@ In both the `required_version` and `required_providers` settings, each override
constraint entirely replaces the constraints for the same component in the
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 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 by Terraform upon merging.

View File

@ -28,6 +28,8 @@ 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.
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, 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.