Creating and switching workspaces in Terraform - Step-by-Step CLI Walkthrough

Introduction

When you work on different versions or environments of your infrastructure, you need a way to keep their settings separate. Terraform workspaces let you create and switch between these separate environments easily.

When you want to manage development and production infrastructure separately using the same Terraform code.

When you need to test changes in a safe environment without affecting the main setup.

When multiple team members work on different features and need isolated infrastructure states.

When you want to keep infrastructure states for different clients or projects separate but use the same configuration.

When you want to quickly switch between different infrastructure setups without changing code.

Commands

This command creates a new workspace named 'dev' to isolate infrastructure state for development.

Terminal

terraform workspace new dev

Expected Output

Created and switched to workspace "dev".



You are now using workspace "dev".

Lists all existing workspaces and shows which one is currently active.

Terminal

terraform workspace list

Expected Output

* default

  dev

Switches the current workspace to 'dev' so that Terraform commands affect this workspace's state.

Terminal

terraform workspace select dev

Expected Output

Switched to workspace "dev".

Shows the name of the currently active workspace to confirm where you are working.

Terminal

terraform workspace show

Expected Output

dev

Key Concept

If you remember nothing else from this pattern, remember: workspaces let you keep different infrastructure states separate using the same Terraform code.

Common Mistakes

Trying to create a workspace with a name that already exists.

Terraform will not create a duplicate workspace and will show an error.

Use 'terraform workspace list' to check existing workspaces before creating a new one.

Running Terraform commands without selecting the correct workspace first.

Terraform will apply changes to the wrong environment, causing confusion or errors.

Always run 'terraform workspace select <name>' to switch to the right workspace before applying changes.

Assuming workspaces isolate everything including variables and backend configuration.

Workspaces only isolate state files; variables and backend settings are shared unless configured separately.

Manage variables and backend settings carefully to avoid conflicts between workspaces.

Summary

Create a new workspace with 'terraform workspace new <name>' to isolate infrastructure state.

List all workspaces and see the current one with 'terraform workspace list'.

Switch between workspaces using 'terraform workspace select <name>' to work on different environments.

Check the active workspace anytime with 'terraform workspace show'.

Practice

1. What is the main purpose of Terraform workspaces?

easy

A. To separate different infrastructure environments

B. To store Terraform state files locally

C. To create new Terraform modules

D. To manage user permissions

Solution

1. Step 1: Understand workspace concept

   Terraform workspaces allow you to manage multiple distinct environments like development and production within the same configuration.

2. Step 2: Identify the purpose

   Separating infrastructure environments helps avoid conflicts and keeps states isolated.

3. Final Answer:

   To separate different infrastructure environments -> Option A

4. Quick Check:

   Workspaces separate environments = A [OK]

Hint: Workspaces isolate environments like folders for projects [OK]

Common Mistakes:

• Confusing workspaces with modules
• Thinking workspaces manage permissions
• Believing workspaces store files locally only

2. Which command correctly creates a new workspace named staging?

easy

A. terraform workspace create staging

B. terraform workspace new staging

C. terraform workspace add staging

D. terraform workspace select staging

Solution

1. Step 1: Recall workspace creation syntax

   The correct command to create a new workspace is terraform workspace new <name>.

2. Step 2: Match the command to the option

   terraform workspace new staging uses terraform workspace new staging, which is correct.

3. Final Answer:

   terraform workspace new staging -> Option B

4. Quick Check:

   Create workspace = terraform workspace new [OK]

Hint: Use 'terraform workspace new' to create workspaces [OK]

Common Mistakes:

• Using 'create' instead of 'new'
• Using 'add' which is invalid
• Confusing 'select' with creation

3. Given the commands:

terraform workspace new test-env
tf workspace select test-env
tf workspace show

What will be the output of terraform workspace show?

medium

A. test-env

B. Error: workspace not found

C. No workspace selected

D. default

Solution

1. Step 1: Analyze command correctness

   The first command terraform workspace new test-env is correct and creates the workspace 'test-env'.

2. Step 2: Identify invalid commands

   The next two commands use the alias tf instead of terraform, which will cause errors unless 'tf' is defined as an alias.

3. Step 3: Determine output of terraform workspace show

   Since tf workspace select test-env likely fails, the workspace is not switched, so terraform workspace show will output the current workspace, which remains default.

4. Final Answer:

   default -> Option D

5. Quick Check:

   Invalid alias causes select to fail, so workspace remains default [OK]

Hint: Use full 'terraform' command unless alias is defined [OK]

Common Mistakes:

• Assuming 'tf' alias works by default
• Expecting workspace switch without correct command
• Ignoring command syntax errors

4. You run terraform workspace select prod but get an error: Workspace 'prod' does not exist. What should you do to fix this?

medium

A. Run terraform workspace new prod to create it first

B. Run terraform init to initialize the workspace

C. Delete the default workspace and retry

D. Run terraform workspace list to delete 'prod'

Solution

1. Step 1: Understand the error

   The error means the workspace 'prod' does not exist yet, so it cannot be selected.

2. Step 2: Create the missing workspace

   You must create it first using terraform workspace new prod before selecting it.

3. Final Answer:

   Run terraform workspace new prod to create it first -> Option A

4. Quick Check:

   Select workspace requires existing workspace [OK]

Hint: Create workspace before selecting it [OK]

Common Mistakes:

• Trying to select without creating
• Running init instead of new
• Deleting default workspace unnecessarily

5. You want to maintain separate Terraform states for dev and prod environments using workspaces. Which sequence of commands correctly sets this up and switches to prod?

hard

A. terraform workspace new prodterraform workspace select dev

B. terraform workspace select devterraform workspace select prod

C. terraform workspace new devterraform workspace new prodterraform workspace select prod

D. terraform workspace new devterraform workspace select devterraform workspace new prod

Solution

1. Step 1: Create both workspaces

   Use terraform workspace new dev and terraform workspace new prod to create separate environments.

2. Step 2: Switch to the desired workspace

   Use terraform workspace select prod to switch to the production environment.

3. Final Answer:

   terraform workspace new dev
   terraform workspace new prod
   terraform workspace select prod -> Option C

4. Quick Check:

   Create then select workspace sequence [OK]

Hint: Create all workspaces before selecting one [OK]

Common Mistakes:

• Selecting workspace before creating it
• Not creating both environments
• Switching to wrong workspace after creation