Local-exec provisioner in Terraform - Time & Space Complexity

Time Complexity: Local-exec provisioner

O(n)

Understanding Time Complexity

We want to understand how the time to run local commands grows when using Terraform's local-exec provisioner.

Specifically, how does running commands on multiple resources affect total execution time?

Scenario Under Consideration

Analyze the time complexity of the following operation sequence.

resource "null_resource" "example" {
  count = var.resource_count

  provisioner "local-exec" {
    command = "echo Resource ${count.index} created"
  }
}

This creates multiple resources, each running a local command after creation.

Identify Repeating Operations

Identify the API calls, resource provisioning, data transfers that repeat.

• Primary operation: Running the local-exec command for each resource.
• How many times: Once per resource, so equal to the number of resources created.

How Execution Grows With Input

Each resource triggers one local command execution, so total commands grow directly with resource count.

Input Size (n)	Approx. API Calls/Operations
10	10 local commands run
100	100 local commands run
1000	1000 local commands run

Pattern observation: The number of local commands grows linearly as the number of resources increases.

Final Time Complexity

Time Complexity: O(n)

This means the total time to run local commands grows directly in proportion to the number of resources.

Common Mistake

[X] Wrong: "Running local-exec commands happens all at once, so time stays the same no matter how many resources."

[OK] Correct: Each local-exec runs separately by default, so more resources mean more commands and more total time.

Interview Connect

Understanding how local-exec scales helps you design Terraform configurations that run efficiently and predictably as your infrastructure grows.

Self-Check

"What if we changed local-exec to run commands in parallel? How would the time complexity change?"

Practice

1. What does the local-exec provisioner do in Terraform?

easy

A. Runs commands inside the cloud resource

B. Executes Terraform plan without applying changes

C. Creates a local copy of the Terraform state file

D. Runs commands on your local machine after resource creation

Solution

1. Step 1: Understand provisioner types

   Terraform provisioners run scripts or commands either locally or remotely after resource creation.

2. Step 2: Identify local-exec purpose

   The local-exec provisioner specifically runs commands on your local machine, not inside the cloud resource.

3. Final Answer:

   Runs commands on your local machine after resource creation -> Option D

4. Quick Check:

   local-exec runs commands locally [OK]

Hint: Local-exec runs commands on your own computer [OK]

Common Mistakes:

• Confusing local-exec with remote-exec
• Thinking it runs inside the cloud resource
• Assuming it manages Terraform state files

2. Which of the following is the correct syntax to use a local-exec provisioner in a Terraform resource?

easy

A. provisioner "local-exec" { command = "echo Hello" }

B. provisioner local-exec { run = "echo Hello" }

C. local_exec { command = "echo Hello" }

D. provisioner "local_exec" { execute = "echo Hello" }

Solution

1. Step 1: Recall Terraform provisioner syntax

   Provisioners use the keyword provisioner followed by the provisioner type in quotes.

2. Step 2: Check correct attribute names

   The local-exec provisioner uses command to specify the shell command to run.

3. Final Answer:

   provisioner "local-exec" { command = "echo Hello" } -> Option A

4. Quick Check:

   Correct syntax uses provisioner "local-exec" and command [OK]

Hint: Use quotes and 'command' attribute for local-exec [OK]

Common Mistakes:

• Omitting quotes around local-exec
• Using wrong attribute names like run or execute
• Using underscore instead of dash in local-exec

3. Given this Terraform snippet, what will happen when the resource is created?

resource "null_resource" "example" {
  provisioner "local-exec" {
    command = "echo Resource created"
  }
}

medium

A. Terraform will fail because null_resource cannot have provisioners

B. Terraform will print 'Resource created' inside the cloud resource

C. Terraform will print 'Resource created' on your local machine

D. Terraform will ignore the provisioner and create the resource silently

Solution

1. Step 1: Understand null_resource and local-exec

   The null_resource is a Terraform resource that supports provisioners for running commands.

2. Step 2: Analyze the command execution

   The local-exec provisioner runs the command on your local machine, so it will print the message locally.

3. Final Answer:

   Terraform will print 'Resource created' on your local machine -> Option C

4. Quick Check:

   local-exec runs commands locally, so output appears locally [OK]

Hint: local-exec runs commands locally, not remotely [OK]

Common Mistakes:

• Thinking output appears inside cloud resource
• Believing null_resource disallows provisioners
• Assuming provisioners are ignored silently

4. You wrote this Terraform code but get an error when applying:

resource "null_resource" "fail_example" {
  provisioner "local-exec" {
    command = echo "Hello"
  }
}

What is the cause of the error?

medium

A. Missing quotes around the command string

B. local-exec provisioner cannot be used with null_resource

C. The command attribute should be named run

D. Terraform does not support echo commands

Solution

1. Step 1: Check command syntax

   The command value must be a string enclosed in quotes in Terraform configuration.

2. Step 2: Identify missing quotes

   Here, command = echo "Hello" lacks quotes around the entire command string, causing a syntax error.

3. Final Answer:

   Missing quotes around the command string -> Option A

4. Quick Check:

   Command must be a quoted string [OK]

Hint: Always quote command strings in local-exec [OK]

Common Mistakes:

• Forgetting quotes around command
• Using wrong attribute names
• Assuming null_resource disallows provisioners

5. You want to run a local script setup.sh after creating an AWS EC2 instance using Terraform. Which is the best way to use local-exec provisioner to achieve this safely?

hard

A. Run setup.sh manually after Terraform apply

B. Use remote-exec provisioner to run setup.sh on the EC2 instance

C. Use local-exec with command = "./setup.sh" inside the EC2 resource without dependencies

D. Use local-exec with command = "./setup.sh" inside the EC2 resource and add depends_on for the instance

Solution

1. Step 1: Understand local-exec vs remote-exec

   The local-exec provisioner runs commands on your local machine, which is not suitable for running scripts on the EC2 instance itself.

2. Step 2: Use remote-exec for remote commands

   To run a script on the EC2 instance, use the remote-exec provisioner which executes commands on the remote resource.

3. Final Answer:

   Use remote-exec provisioner to run setup.sh on the EC2 instance -> Option B

4. Quick Check:

   remote-exec runs commands on the remote resource [OK]

Hint: Use remote-exec to run scripts on remote instances [OK]

Common Mistakes:

• Using remote-exec for a local script
• Running scripts manually instead of automating
• Adding unnecessary depends_on inside the resource