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

Explain purpose of environments better (#14869)

This commit is contained in:
Radek Simko 2017-05-26 20:34:23 +01:00 committed by GitHub
parent 46be301806
commit 4da1b46d35
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -83,12 +83,13 @@ resource "aws_instance" "example" {
## Best Practices ## Best Practices
An environment alone **should not** be used to manage the difference between An environment can be used to manage the difference between development,
development, staging, and production. As Terraform configurations get larger, staging, and production, but it **should not** be treated as the only isolation
it's much more manageable and safer to split one large configuration into many mechanism. As Terraform configurations get larger, it's much more
smaller ones linked together with terraform_remote_state data sources. This manageable and safer to split one large configuration into many
smaller ones linked together with `terraform_remote_state` data sources. This
allows teams to delegate ownership and reduce the blast radius of changes. allows teams to delegate ownership and reduce the blast radius of changes.
For each smaller configuration, you can use environments to model the For **each smaller configuration**, you can use environments to model the
differences between development, staging, and production. However, if you have differences between development, staging, and production. However, if you have
one large Terraform configuration, it is riskier and not recommended to use one large Terraform configuration, it is riskier and not recommended to use
environments to model those differences. environments to model those differences.