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

Merge pull request #30649 from dragondrop-cloud/main 

Documentation Update: Capture `cloud`/ `backend` block override behavior in docs
This commit is contained in:
Laura Pacilio 2022-03-15 16:47:23 -04:00 committed by GitHub
parent 24d174d36e 659fb09fc1
commit 50d49d0b0d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -150,3 +150,11 @@ In both the `required_version` and `required_providers` settings, each override
constraint entirely replaces the constraints for the same component in the 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.
The presence of a block defining a backend (either `cloud` or `backend`) in an override
file always takes precedence over a block defining a backend in the original configuration.
That is, if a `cloud` block is set within the original configuration and a `backend` block is
set in the override file, Terraform will use the `backend` block specified in the override file 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 upon merging.