Why Default workspace in Terraform? - Purpose & Use Cases

The Big Idea

What if one simple setting could save you hours of confusion and costly mistakes?

The Scenario

Imagine you manage multiple projects on your computer, but you keep saving all files in the same folder without organizing them.

When you want to find a specific file, you waste time searching or risk opening the wrong one.

The Problem

Manually switching between projects or environments is slow and confusing.

You might accidentally overwrite settings or deploy changes to the wrong place.

This causes errors and extra work fixing problems.

The Solution

Default workspace in Terraform acts like a dedicated folder for each project or environment.

It keeps your infrastructure settings separate and organized automatically.

This way, you avoid mix-ups and can work faster and safer.

Before vs After

✗ Before

terraform apply -var='env=prod'
terraform apply -var='env=dev'

✓ After

terraform workspace select default
terraform apply
terraform workspace select dev
terraform apply

What It Enables

It enables you to manage multiple environments cleanly without mixing configurations or risking mistakes.

Real Life Example

A developer can switch between testing and production environments easily, ensuring changes are applied only where intended.

Key Takeaways

Manual management of environments is error-prone and slow.

Default workspace organizes infrastructure states automatically.

This leads to safer, faster, and clearer cloud deployments.

Practice

1. What is the default workspace in Terraform?

easy

A. A workspace only for remote backends

B. A workspace you must create manually before use

C. A temporary workspace that deletes after each run

D. The main workspace Terraform uses automatically to store state

Solution

1. Step 1: Understand Terraform workspaces

   Terraform uses workspaces to manage different states. The default workspace is created automatically.

2. Step 2: Identify the role of the default workspace

   The default workspace stores the state unless you create and switch to others.

3. Final Answer:

   The main workspace Terraform uses automatically to store state -> Option D

4. Quick Check:

   Default workspace = main automatic workspace [OK]

Hint: Default workspace is automatic and stores state by default [OK]

Common Mistakes:

• Thinking default workspace must be created manually
• Assuming default workspace deletes after runs
• Confusing default workspace with remote backend only

2. Which command shows the current active workspace in Terraform?

easy

A. terraform workspace list

B. terraform workspace show

C. terraform workspace current

D. terraform workspace status

Solution

1. Step 1: Recall Terraform workspace commands

   Common commands include list to see all workspaces and show to display the current one.

2. Step 2: Identify the command to show active workspace

   terraform workspace show outputs the current active workspace name.

3. Final Answer:

   terraform workspace show -> Option B

4. Quick Check:

   Show current workspace = terraform workspace show [OK]

Hint: Use 'terraform workspace show' to see active workspace [OK]

Common Mistakes:

• Using 'terraform workspace list' to show current workspace
• Assuming 'terraform workspace current' is valid
• Confusing 'status' with workspace commands

3. Given this Terraform CLI output after running terraform workspace list:

  default
* dev
  staging

Which workspace is currently active?

medium

A. default

B. staging

C. dev

D. No workspace is active

Solution

1. Step 1: Understand workspace list output format

   The asterisk (*) marks the currently active workspace in the list.

2. Step 2: Identify the active workspace

   The workspace with * is dev, so it is active.

3. Final Answer:

   dev -> Option C

4. Quick Check:

   Asterisk marks active workspace = dev [OK]

Hint: Look for * in workspace list to find active workspace [OK]

Common Mistakes:

• Choosing 'default' because it sounds like default
• Ignoring the asterisk symbol
• Assuming no workspace is active if not obvious

4. You run terraform workspace new test but get an error: "Workspace 'test' already exists." What should you do next?

medium

A. Run terraform workspace select test to switch to it

B. Delete the existing workspace with terraform workspace delete test

C. Rename the existing workspace before creating a new one

D. Run terraform init again to fix the error

Solution

1. Step 1: Understand the error message

   The error says the workspace already exists, so you cannot create it again.

2. Step 2: Choose the correct action

   Since it exists, you should switch to it using terraform workspace select test.

3. Final Answer:

   Run terraform workspace select test to switch to it -> Option A

4. Quick Check:

   Workspace exists? Select it, don't create [OK]

Hint: Select existing workspace instead of creating it again [OK]

Common Mistakes:

• Trying to create workspace again without switching
• Deleting workspace unnecessarily
• Running init does not fix workspace existence

5. You want to manage two environments, prod and dev, using Terraform workspaces. Which approach correctly uses the default workspace?

hard

A. Use default workspace for dev and create/select prod workspace

B. Create both prod and dev workspaces and never use default

C. Rename default workspace to prod and create dev workspace

D. Use the default workspace for prod and create/select dev workspace

Solution

1. Step 1: Understand default workspace role

   The default workspace is ready to use and often used for simpler or initial environments.

2. Step 2: Apply best practice for environment separation

   Use default for dev (development) and create/select a separate workspace for prod (production) to isolate states.

3. Final Answer:

   Use default workspace for dev and create/select prod workspace -> Option A

4. Quick Check:

   Default workspace = dev environment [OK]

Hint: Use default for dev, create prod workspace for safety [OK]

Common Mistakes:

• Using default for prod which risks accidental changes
• Ignoring default workspace and creating all manually
• Trying to rename default workspace (not supported)