Terraform CLI overview - Time & Space Complexity

Time Complexity: Terraform CLI overview

O(n)

Understanding Time Complexity

We want to understand how the time to run Terraform commands changes as we manage more resources.

Specifically, how does the number of resources affect the work Terraform CLI does?

Scenario Under Consideration

Analyze the time complexity of running Terraform plan and apply on multiple resources.

resource "aws_instance" "example" {
  count         = var.instance_count
  ami           = "ami-123456"
  instance_type = "t2.micro"
}

output "instance_ids" {
  value = aws_instance.example[*].id
}
    

This code creates a number of virtual machines based on the input count variable.

Identify Repeating Operations

Terraform performs these repeated actions:

• Primary operation: API calls to create or update each virtual machine resource.
• How many times: Once per resource, so equal to the number of instances specified.

How Execution Grows With Input

As you increase the number of instances, the number of API calls grows in the same way.

Input Size (n)	Approx. API Calls/Operations
10	About 10 API calls
100	About 100 API calls
1000	About 1000 API calls

Pattern observation: The work grows directly with the number of resources.

Final Time Complexity

Time Complexity: O(n)

This means the time to run Terraform commands grows linearly with the number of resources.

Common Mistake

[X] Wrong: "Terraform runs all resources in constant time no matter how many there are."

[OK] Correct: Each resource requires separate API calls and processing, so more resources mean more work.

Interview Connect

Understanding how Terraform scales with resource count helps you design efficient infrastructure and shows you grasp cloud automation basics.

Self-Check

"What if we used modules that create multiple resources inside? How would that affect the time complexity?"

Practice

1. What is the primary purpose of the terraform init command?

easy

A. To show the planned changes without applying them

B. To apply changes to cloud infrastructure

C. To destroy all managed resources

D. To initialize a working directory and download required provider plugins

Solution

1. Step 1: Understand the role of terraform init

   This command sets up the working directory by downloading necessary provider plugins and preparing the environment.

2. Step 2: Differentiate from other commands

   Commands like apply and destroy perform changes, while init only prepares the setup.

3. Final Answer:

   To initialize a working directory and download required provider plugins -> Option D

4. Quick Check:

   terraform init prepares environment [OK]

Hint: Init sets up your folder and downloads plugins [OK]

Common Mistakes:

• Confusing init with apply
• Thinking init changes infrastructure
• Mixing init with destroy

2. Which of the following is the correct syntax to preview changes without applying them?

easy

A. terraform plan

B. terraform apply --preview

C. terraform preview

D. terraform show

Solution

1. Step 1: Identify the command to preview changes

   terraform plan shows what changes will happen without applying them.

2. Step 2: Check other options for correctness

   apply --preview and preview are not valid commands; show displays current state, not planned changes.

3. Final Answer:

   terraform plan -> Option A

4. Quick Check:

   Preview changes = terraform plan [OK]

Hint: Plan shows changes without applying [OK]

Common Mistakes:

• Using apply --preview which is invalid
• Confusing show with plan
• Assuming preview is a Terraform command

3. Given the following sequence of commands:

terraform init
tf plan
terraform apply

What will happen when you run these commands?

medium

A. Only initialize the directory and apply changes, skipping the plan

B. Initialize the directory, show planned changes, then apply those changes

C. Initialize the directory, apply changes immediately, then show the plan

D. Show planned changes without initializing or applying

Solution

1. Step 1: Understand each command's role

   terraform init sets up the environment, terraform plan shows what will change, and terraform apply makes those changes.

2. Step 2: Analyze the sequence

   The commands run in order: initialize, plan, then apply, which is the recommended workflow.

3. Final Answer:

   Initialize the directory, show planned changes, then apply those changes -> Option B

4. Quick Check:

   Init -> Plan -> Apply = safe workflow [OK]

Hint: Init, then plan, then apply changes [OK]

Common Mistakes:

• Running apply before plan
• Skipping init before plan
• Confusing plan and apply order

4. You run terraform apply but get an error saying the backend is not configured. What is the most likely cause?

medium

A. You need to run terraform destroy first

B. You used the wrong syntax for apply

C. You forgot to run terraform init first

D. Your cloud provider credentials are missing

Solution

1. Step 1: Understand backend configuration role

   The backend stores state remotely and must be set up before applying changes.

2. Step 2: Identify how backend is configured

   terraform init configures the backend; skipping it causes errors.

3. Final Answer:

   You forgot to run terraform init first -> Option C

4. Quick Check:

   Init configures backend before apply [OK]

Hint: Always run init before apply to configure backend [OK]

Common Mistakes:

• Skipping init and running apply directly
• Assuming credentials cause backend error
• Thinking destroy fixes backend issues

5. You want to safely remove all cloud resources managed by Terraform. Which command sequence ensures this with minimal risk?

hard

A. terraform destroy after terraform plan to review changes

B. terraform apply followed by terraform destroy

C. terraform init then terraform apply

D. terraform plan then terraform init

Solution

1. Step 1: Understand the purpose of terraform destroy

   This command deletes all resources managed by Terraform.

2. Step 2: Use terraform plan before destroy

   Planning shows what will be destroyed, helping avoid mistakes.

3. Step 3: Confirm the sequence

   Running terraform plan first, then terraform destroy is the safest approach.

4. Final Answer:

   terraform destroy after terraform plan to review changes -> Option A

5. Quick Check:

   Plan before destroy to avoid surprises [OK]

Hint: Plan first, then destroy to confirm changes [OK]

Common Mistakes:

• Destroying without planning first
• Applying changes before destroying
• Running init after plan