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

website: environment at scale wording

This commit is contained in:
Mitchell Hashimoto 2017-03-16 23:37:24 -07:00
parent abbc3b66e2
commit 36f749f825
No known key found for this signature in database
GPG Key ID: 744E147AA52F5B0A
1 changed files with 8 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
website/source/docs/state/environments.html.md
View File

@ -79,11 +79,14 @@ resource "aws_instance" "example" {
## Best Practices ## Best Practices
An environment alone **should not** be used to manage the difference between An environment alone **should not** be used to manage the difference between
development, staging, and production. While it is technically possible, it is development, staging, and production. As Terraform configurations get larger,
much more manageable and safe to use multiple independently managed Terraform it's much more manageable and safer to split one large configuration into many
configurations linked together with smaller ones linked together with terraform_remote_state data sources. This
[terraform_remote_state](/docs/providers/terraform/d/remote_state.html) allows teams to delegate ownership and reduce the blast radius of changes.
data sources. For each smaller configuration, you can use environments to model the
differences between development, staging, and production. However, if you have
one large Terraform configuration, it is riskier and not recommended to use
environments to model those differences.
The [terraform_remote_state](/docs/providers/terraform/d/remote_state.html) The [terraform_remote_state](/docs/providers/terraform/d/remote_state.html)
resource accepts an `environment` name to target. Therefore, you can link resource accepts an `environment` name to target. Therefore, you can link