IntenseWebs/opentofu
3
0
Fork 0
mirror of https://github.com/opentofu/opentofu.git synced 2025-01-08 23:23:59 -06:00
Code Issues Packages Projects Releases Wiki Activity

make collaboration more important

Browse Source
This commit is contained in:
Kevin Fishner 2015-04-20 15:32:59 -07:00
parent e2b6989606
commit 0f61ac85de
1 changed files with 17 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
website/source/intro/getting-started/remote.html.markdown
View File

@ -11,16 +11,25 @@ We've now seen how to build, change, and destroy infrastructure
from a local machine. This is great for testing and development, from a local machine. This is great for testing and development,
however in production environments it is more responsible to run however in production environments it is more responsible to run
Terraform remotely and store a master Terraform state remotely. Terraform remotely and store a master Terraform state remotely.
Otherwise it's possible for multiple different Terraform states
to be stored on developer machines, which could lead to conflicts. [Atlas](https://atlas.hashicorp.com/?utm_source=oss&utm_medium=getting-started&utm_campaign=terraform)
Additionally by running Terraform remotely, you can move access is HashiCorp's solution for Terraform remote runs and
credentials off of developer machines, release local machines from infrastructure version control. Running Terraform
long-running Terraform processes, and store a history of in Atlas allows teams to easily version, audit, and collaborate
infrastructure changes to help with auditing and collaboration. on infrastructure changes. Each proposed change generates
a Terraform plan which can be reviewed and collaborated on as a team.
When a proposed change is accepted, the Terraform logs are stored
in Atlas, resulting in a linear history of infrastructure states to
help with auditing and policy enforcement. Additional benefits to
running Terraform remotely include moving access
credentials off of developer machines and releasing local machines
from long-running Terraform processes.
# How to Use Terraform Remotely # How to Use Terraform Remotely
Using Terraform remotely is straightforward with [Atlas by HashiCorp](https://atlas.hashicorp.com/?utm_source=oss&utm_medium=getting-started&utm_campaign=terraform). You can learn how to use Terraform remotely with our [interactive tutorial](https://atlas.hashicorp.com/tutorial/terraform/?utm_source=oss&utm_medium=getting-started&utm_campaign=terraform),
You first need to configure [Terraform remote state storage](/docs/commands/remote.html) or you can follow the outlined steps below.
First, configure [Terraform remote state storage](/docs/commands/remote.html)
with the command: with the command:
``` ```