Workspaces vs directory-based separation in Terraform - Quick Revision & Key Differences

Recall & Review

beginner

What is a Terraform workspace?

A Terraform workspace is a way to have multiple instances of the same infrastructure configuration, each with its own state, allowing you to manage different environments like dev, test, and prod within the same directory.

beginner

How does directory-based separation differ from using workspaces in Terraform?

Directory-based separation means creating separate folders for each environment with its own Terraform files and state, while workspaces use one directory but switch states internally to manage multiple environments.

intermediate

What is a key advantage of using Terraform workspaces over directory-based separation?

Workspaces allow you to reuse the same configuration files for multiple environments, reducing duplication and making it easier to maintain consistent infrastructure setups.

intermediate

What is a potential downside of using Terraform workspaces?

Workspaces can be confusing because the same configuration is used for all environments, so mistakes in variable values or state management can affect multiple environments if not handled carefully.

intermediate

When might directory-based separation be preferred over workspaces?

Directory-based separation is preferred when environments have very different configurations or when teams want clear physical separation of code and state files to avoid accidental changes across environments.

What does a Terraform workspace primarily manage?

A Separate state files for different environments

B Different Terraform versions

C Multiple cloud providers in one config

D User access permissions

Terraform workspaces manage separate state files so you can have multiple environments using the same configuration.

Which method involves creating separate folders for each environment?

A Remote state backend

B Terraform workspaces

C Terraform modules

D Directory-based separation

Directory-based separation means using different folders for each environment.

What is a benefit of using workspaces instead of directories?

A Easier to maintain one set of configuration files

B Better security isolation

C Supports different Terraform versions per environment

D Allows multiple cloud providers in one workspace

Workspaces let you reuse the same configuration files for multiple environments.

Which is a risk when using Terraform workspaces?

A Cannot use variables

B Duplicating configuration files

C Accidentally applying changes to the wrong environment

D Hard to share state files

Because workspaces share the same config, applying changes to the wrong workspace can affect the wrong environment.

When is directory-based separation most useful?

A When you want to use one state file

B When environments have very different configurations

C When you want to avoid using variables

D When using only one environment

Directory-based separation is best when environments differ a lot and need separate configs.

Explain the difference between Terraform workspaces and directory-based separation.

Think about how state and configuration files are organized.

Describe a scenario where you would choose Terraform workspaces over directory-based separation.

Consider when reusing configuration is helpful.

Practice

1. What is the main difference between Terraform workspaces and directory-based separation?

easy

A. Workspaces require separate folders; directory-based uses one folder with multiple states.

B. Workspaces store state remotely; directory-based stores state locally only.

C. Workspaces and directory-based separation are exactly the same.

D. Workspaces use one folder with multiple states; directory-based uses separate folders for each environment.

Solution

1. Step 1: Understand workspace concept

   Workspaces allow multiple states inside the same folder by switching context.

2. Step 2: Understand directory-based separation

   Directory-based separation uses different folders, each with its own code and state files.

3. Final Answer:

   Workspaces use one folder with multiple states; directory-based uses separate folders for each environment. -> Option D

4. Quick Check:

   Workspaces = one folder, multiple states [OK]

Hint: Workspaces = one folder, directory = multiple folders [OK]

Common Mistakes:

• Confusing workspace with directory-based separation
• Thinking workspaces require multiple folders
• Assuming directory-based uses one state file

2. Which Terraform command correctly switches to a workspace named dev?

easy

A. terraform workspace select dev

B. terraform select workspace dev

C. terraform switch workspace dev

D. terraform workspace change dev

Solution

1. Step 1: Recall Terraform workspace commands

   The correct command to switch workspace is terraform workspace select <name>.

2. Step 2: Match command to options

   Only terraform workspace select dev matches the correct syntax exactly.

3. Final Answer:

   terraform workspace select dev -> Option A

4. Quick Check:

   Switch workspace = terraform workspace select [OK]

Hint: Use 'terraform workspace select' to switch workspaces [OK]

Common Mistakes:

• Using incorrect command order
• Using non-existent commands like 'switch' or 'change'
• Confusing workspace commands with other terraform commands

3. Given this folder structure:

envs/
  ├─ dev/
  │    └─ main.tf
  └─ prod/
       └─ main.tf

and using directory-based separation, what happens if you run terraform apply inside envs/dev?

medium

A. Terraform applies changes to both dev and prod environments simultaneously.

B. Terraform applies changes only to the dev environment using its own state.

C. Terraform throws an error because state is missing.

D. Terraform applies changes to the prod environment instead.

Solution

1. Step 1: Understand directory-based separation behavior

   Each folder has its own Terraform code and state, so running inside envs/dev affects only dev.

2. Step 2: Analyze command effect

   terraform apply in envs/dev applies changes only to dev environment's resources.

3. Final Answer:

   Terraform applies changes only to the dev environment using its own state. -> Option B

4. Quick Check:

   Directory-based apply affects current folder environment [OK]

Hint: Apply runs in current folder's environment only [OK]

Common Mistakes:

• Assuming apply affects all environments
• Thinking state is shared across folders
• Expecting errors due to missing state

4. You created a new workspace named staging but when running terraform apply, changes apply to the default workspace instead. What is the likely cause?

medium

A. You forgot to run terraform workspace select staging before applying.

B. The staging workspace does not exist.

C. Terraform does not support multiple workspaces.

D. You need to rename the default workspace to staging.

Solution

1. Step 1: Check workspace usage

   Creating a workspace does not switch to it automatically; you must select it explicitly.

2. Step 2: Identify missing command

   If you don't run terraform workspace select staging, Terraform stays in default workspace.

3. Final Answer:

   You forgot to run terraform workspace select staging before applying. -> Option A

4. Quick Check:

   Must select workspace before apply [OK]

Hint: Always select workspace before applying changes [OK]

Common Mistakes:

• Assuming workspace auto-switches after creation
• Thinking workspace names must be renamed
• Believing Terraform lacks workspace support

5. You want to manage three environments: dev, staging, and prod. You want to keep code DRY (Don't Repeat Yourself) and share most configuration but keep states isolated. Which approach is best?

hard

A. Use one folder and switch backend configuration files for each environment.

B. Create three separate folders, each with full copies of code and state.

C. Use one folder with Terraform workspaces for each environment.

D. Use one folder and manually rename state files for each environment.

Solution

1. Step 1: Analyze DRY and state isolation needs

   Sharing code but isolating state fits well with workspaces, which share code folder but separate states.

2. Step 2: Compare options

   Use one folder with Terraform workspaces for each environment uses workspaces to keep one codebase and separate states per environment, avoiding code duplication.

3. Step 3: Evaluate other options

   Create three separate folders, each with full copies of code and state duplicates code, violating DRY. Use one folder and manually rename state files for each environment is error-prone and manual. Use one folder and switch backend configuration files for each environment requires backend changes, complex to manage.

4. Final Answer:

   Use one folder with Terraform workspaces for each environment. -> Option C

5. Quick Check:

   Workspaces = shared code, separate states [OK]

Hint: Workspaces share code, separate states for DRY environments [OK]

Common Mistakes:

• Duplicating code in multiple folders unnecessarily
• Trying manual state file renaming
• Switching backend configs frequently