More mentions of remote backend

This commit is contained in:
Laura Pacilio 2021-12-21 17:51:06 -05:00
parent caf0bdbe8d
commit 138ca02b90
3 changed files with 6 additions and 9 deletions

View File

@ -20,9 +20,7 @@ It is safe to run this command automatically, for example as a post-save
check in a text editor or as a test step for a re-usable module in a CI check in a text editor or as a test step for a re-usable module in a CI
system. system.
Validation requires an initialized working directory with any referenced Validation requires an initialized working directory with any referenced plugins and modules installed. To initialize a working directory for validation without accessing any configured backend, use:
plugins and modules installed. To initialize a working directory for
validation without accessing any configured remote backend, use:
``` ```
$ terraform init -backend=false $ terraform init -backend=false

View File

@ -88,7 +88,7 @@ be separated by spaces otherwise.
## TF_DATA_DIR ## TF_DATA_DIR
`TF_DATA_DIR` changes the location where Terraform keeps its `TF_DATA_DIR` changes the location where Terraform keeps its
per-working-directory data, such as the current remote backend configuration. per-working-directory data, such as the current backend configuration.
By default this data is written into a `.terraform` subdirectory of the By default this data is written into a `.terraform` subdirectory of the
current directory, but the path given in `TF_DATA_DIR` will be used instead current directory, but the path given in `TF_DATA_DIR` will be used instead

View File

@ -38,13 +38,12 @@ imported object will be mapped.
While this may seem tedious, it still gives Terraform users an avenue for While this may seem tedious, it still gives Terraform users an avenue for
importing existing resources. importing existing resources.
## Remote Backends ## Terraform Cloud
When using Terraform import on the command line with a [remote When using Terraform import on the command line with Terraform Cloud, the import
backend](/language/settings/backends/remote), such as Terraform Cloud, the import
command runs locally, unlike commands such as apply, which run inside your command runs locally, unlike commands such as apply, which run inside your
Terraform Cloud environment. Because of this, the import command will not have Terraform Cloud environment. Because of this, the import command will not have
access to information from the remote backend, such as workspace variables. access to information from Terraform Cloud, such as workspace variables.
In order to use Terraform import with a remote state backend, you may need to In order to use Terraform import with Terraform Cloud, you may need to
set local variables equivalent to the remote workspace variables. set local variables equivalent to the remote workspace variables.