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

docs: Update getting-started guide to suggest remote-state

This commit is contained in:
stack72 2016-12-08 12:53:34 +01:00
parent ff8c948cf5
commit 32b81ab209
No known key found for this signature in database
GPG Key ID: 8619A619B085CB16
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/source/intro/getting-started/build.html.md
View File

@ -179,10 +179,10 @@ Terraform also puts some state into the `terraform.tfstate` file
by default. This state file is extremely important; it maps various by default. This state file is extremely important; it maps various
resource metadata to actual resource IDs so that Terraform knows resource metadata to actual resource IDs so that Terraform knows
what it is managing. This file must be saved and distributed what it is managing. This file must be saved and distributed
to anyone who might run Terraform. This file generally isn't too large, to anyone who might run Terraform. It is generally recommended to
and for most simple setups, the file might be added to version control along [setup remote state](https://www.terraform.io/docs/state/remote/index.html)
with rest of the Terraform code. For larger teams, it might be when working with Terraform. This will mean that any potential secrets
beneficial to [setup remote state](https://www.terraform.io/docs/state/remote/index.html). stored in the state file, will not be checked into version control
You can inspect the state using `terraform show`: You can inspect the state using `terraform show`: