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

fix: suggested changes

This commit is contained in:
GoodmanBen 2022-03-14 19:03:53 -04:00
parent b1532c4318
commit e9043cdcad
2 changed files with 9 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -151,7 +151,10 @@ constraint entirely replaces the constraints for the same component in the
original block. If both the base block and the override block both set 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. `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 The presence of a block defining a backend (either `cloud` or `backend`) in an override
is set in the override file, then the backend specified by the `backend` block is used by Terraform upon merging. file always takes precedence over a block defining a backend in the original configuration.
Similarly, if a `backend` block is set within the original configuration's `terraform` block That is, if a `cloud` block is set within the original configuration and a `backend` block is
and a `cloud` block is set in the override file, then the backend specified by the `backend` block is used by Terraform upon merging. set in the override file, Terraform will use the `backend` block specified in the override file as the
configuration's backend upon merging. Similarly, if a `backend` block is set within the original
configuration and a `cloud` block is set in the override file, Terraform will use the `cloud`
block specified in the override file as the configuration's backend upon merging.

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

@ -30,6 +30,7 @@ terraform {
You cannot use the CLI integration and a [state backend](/language/settings/backends) in the same configuration; they are mutually exclusive. 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. 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). However, if a state `backend` block is defined in an [override file](/language/files/override),
that `backend` block will override an existing `cloud` block in the configuration upon merging.
Refer to [Using Terraform Cloud](/cli/cloud) in the Terraform CLI docs for more information. Refer to [Using Terraform Cloud](/cli/cloud) in the Terraform CLI docs for more information.