When workspaces are appropriate in Terraform - Step-by-Step Execution

Process Flow - When workspaces are appropriate

Start Terraform Project

↓

Decide Environment Separation?

↓

Use Workspaces

↓

Deploy Resources

↓

Manage State

↓

End

This flow shows deciding if Terraform workspaces are needed to separate environments, then deploying resources accordingly.

Execution Sample

Terraform

terraform workspace new dev
terraform apply
terraform workspace new prod
terraform apply

Create separate workspaces for dev and prod environments and apply infrastructure changes in each.

Process Table

Step	Action	Workspace	State File Used	Result
1	Create workspace 'dev'	dev	terraform.tfstate (dev)	Workspace 'dev' created
2	Apply infrastructure	dev	terraform.tfstate (dev)	Resources deployed in dev
3	Create workspace 'prod'	prod	terraform.tfstate (prod)	Workspace 'prod' created
4	Apply infrastructure	prod	terraform.tfstate (prod)	Resources deployed in prod
5	Switch to 'dev'	dev	terraform.tfstate (dev)	Workspace switched to dev
6	Destroy infrastructure	dev	terraform.tfstate (dev)	Resources destroyed in dev
7	Switch to 'prod'	prod	terraform.tfstate (prod)	Workspace switched to prod
8	Destroy infrastructure	prod	terraform.tfstate (prod)	Resources destroyed in prod

💡 All environments managed separately using workspaces, ensuring isolated state files.

Status Tracker

Variable	Start	After Step 1	After Step 3	After Step 5	After Step 7	Final
Current Workspace	default	dev	prod	dev	prod	prod
State File	terraform.tfstate (default)	terraform.tfstate (dev)	terraform.tfstate (prod)	terraform.tfstate (dev)	terraform.tfstate (prod)	terraform.tfstate (prod)

Key Moments - 2 Insights

Why do we create separate workspaces for dev and prod instead of using one?

Separate workspaces keep state files isolated, so changes in dev do not affect prod. See steps 1-4 in execution_table.

What happens if we apply infrastructure without switching to the correct workspace?

Terraform will apply changes to the current workspace's state, possibly affecting the wrong environment. See step 5 and 7 for switching workspaces.

Visual Quiz - 3 Questions

Look at the execution_table, what workspace is active after step 3?

A default

B dev

C prod

D none

💡 Hint

Check the 'Workspace' column at step 3 in execution_table.

At which step does Terraform switch back to the 'dev' workspace?

A Step 5

B Step 7

C Step 2

D Step 4

💡 Hint

Look for 'Switch to dev' action in execution_table.

If you did not create separate workspaces, what would happen to the state files?

A Separate state files automatically created

B One shared state file for all environments

C No state file created

D State files deleted after apply

💡 Hint

Refer to variable_tracker showing state file names per workspace.

Concept Snapshot

Terraform workspaces let you manage multiple environments in one project.
Each workspace has its own state file.
Use 'terraform workspace new <name>' to create.
Switch with 'terraform workspace select <name>'.
Apply changes per workspace to isolate environments.

Full Transcript

This visual execution shows when to use Terraform workspaces. You start by deciding if you need separate environments like dev and prod. If yes, create a workspace for each. Each workspace has its own state file, so changes in one do not affect the other. You apply infrastructure changes in each workspace separately. Switching workspaces changes which environment you manage. This keeps your infrastructure organized and safe. The execution table traces creating workspaces, applying resources, switching, and destroying them. The variable tracker shows how the current workspace and state file change over time. Key moments clarify why isolation matters and what happens if you don't switch workspaces. The quiz tests understanding of workspace states and effects on state files.