mirror of
https://github.com/opentofu/opentofu.git
synced 2025-02-25 18:45:20 -06:00
Move TFC workspaces section further down
This commit is contained in:
parent
35a5e92687
commit
f7bf19525e
@ -21,16 +21,6 @@ Use the [`terraform workspace list`](/cli/commands/workspace/list), [`terraform
|
|||||||
|
|
||||||
Use [the `terraform workspace select` command](/cli/commands/workspace/select) to change the currently selected workspace. For a given working directory, you can only select one workspace can be at a time. Most Terraform commands only interact with the currently selected workspace. This includes [provisioning](/cli/run) and [state manipulation](/cli/state).
|
Use [the `terraform workspace select` command](/cli/commands/workspace/select) to change the currently selected workspace. For a given working directory, you can only select one workspace can be at a time. Most Terraform commands only interact with the currently selected workspace. This includes [provisioning](/cli/run) and [state manipulation](/cli/state).
|
||||||
|
|
||||||
## Interactions with Terraform Cloud Workspaces
|
|
||||||
|
|
||||||
Terraform Cloud organizes infrastructure using workspaces, but its workspaces
|
|
||||||
act more like completely separate working directories. Each Terraform Cloud
|
|
||||||
workspace has its own Terraform configuration, set of variable values, state
|
|
||||||
data, run history, and settings.
|
|
||||||
|
|
||||||
When you [integrate Terraform CLI with Terraform Cloud](/cli/cloud), you can associate the current CLI working directory with one or more remote Terraform Cloud workspaces. Then, use the `terraform workspace` commands to select the remote workspace you want to use for each run.
|
|
||||||
|
|
||||||
Refer to [CLI-driven Runs](/cloud-docs/run/cli) in the Terraform Cloud documentation for more details.
|
|
||||||
|
|
||||||
## Use Cases
|
## Use Cases
|
||||||
|
|
||||||
@ -88,6 +78,18 @@ When multiple configurations represent distinct system components rather than mu
|
|||||||
configurations. This creates a tighter coupling between configurations,
|
configurations. This creates a tighter coupling between configurations,
|
||||||
but avoids the need for the "producer" configuration to explicitly
|
but avoids the need for the "producer" configuration to explicitly
|
||||||
publish its results in a separate system.
|
publish its results in a separate system.
|
||||||
|
|
||||||
|
|
||||||
|
## Interactions with Terraform Cloud Workspaces
|
||||||
|
|
||||||
|
Terraform Cloud organizes infrastructure using workspaces, but its workspaces
|
||||||
|
act more like completely separate working directories. Each Terraform Cloud
|
||||||
|
workspace has its own Terraform configuration, set of variable values, state
|
||||||
|
data, run history, and settings.
|
||||||
|
|
||||||
|
When you [integrate Terraform CLI with Terraform Cloud](/cli/cloud), you can associate the current CLI working directory with one or more remote Terraform Cloud workspaces. Then, use the `terraform workspace` commands to select the remote workspace you want to use for each run.
|
||||||
|
|
||||||
|
Refer to [CLI-driven Runs](/cloud-docs/run/cli) in the Terraform Cloud documentation for more details.
|
||||||
|
|
||||||
|
|
||||||
## Workspace Internals
|
## Workspace Internals
|
||||||
|
Loading…
Reference in New Issue
Block a user