From 4da1b46d3512db772c849466b7dfb73ea5786695 Mon Sep 17 00:00:00 2001 From: Radek Simko Date: Fri, 26 May 2017 20:34:23 +0100 Subject: [PATCH] Explain purpose of environments better (#14869) --- website/source/docs/state/environments.html.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/website/source/docs/state/environments.html.md b/website/source/docs/state/environments.html.md index b7f3e2a3c..b18433ba0 100644 --- a/website/source/docs/state/environments.html.md +++ b/website/source/docs/state/environments.html.md @@ -83,12 +83,13 @@ resource "aws_instance" "example" { ## Best Practices -An environment alone **should not** be used to manage the difference between -development, staging, and production. As Terraform configurations get larger, -it's much more manageable and safer to split one large configuration into many -smaller ones linked together with terraform_remote_state data sources. This +An environment can be used to manage the difference between development, +staging, and production, but it **should not** be treated as the only isolation +mechanism. As Terraform configurations get larger, it's much more +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. -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 one large Terraform configuration, it is riskier and not recommended to use environments to model those differences.