Provisioner failure behavior in Terraform - Time & Space Complexity

Time Complexity: Provisioner failure behavior

O(n)

Understanding Time Complexity

When Terraform runs provisioners, it may retry or stop on failure. Understanding how the time taken grows with the number of provisioners helps us plan deployments better.

We want to know how the total execution time changes as we add more provisioners that might fail.

Scenario Under Consideration

Analyze the time complexity of running multiple local-exec provisioners with failure handling.

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

  provisioner "local-exec" {
    command = "echo Running provisioner ${count.index}"
    on_failure = "continue"
  }
}

This creates multiple resources each with a local-exec provisioner that continues even if it fails.

Identify Repeating Operations

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

• Primary operation: Running each local-exec provisioner command.
• How many times: Once per provisioner, equal to the number of provisioners defined.

How Execution Grows With Input

Each provisioner runs its command independently. As you add more provisioners, the total time grows roughly in direct proportion.

Input Size (n)	Approx. API Calls/Operations
10	10 provisioner runs
100	100 provisioner runs
1000	1000 provisioner runs

Pattern observation: The total execution time increases linearly as the number of provisioners increases.

Final Time Complexity

Time Complexity: O(n)

This means the time to run all provisioners grows directly with how many provisioners you have.

Common Mistake

[X] Wrong: "Provisioners run in parallel, so adding more won't increase total time much."

[OK] Correct: By default, provisioners run one after another, so adding more means more total time.

Interview Connect

Knowing how provisioner failures affect deployment time helps you design reliable and predictable infrastructure automation.

Self-Check

"What if we changed on_failure from 'continue' to 'fail'? How would the time complexity change when a provisioner fails early?"

Practice

1.

What does the on_failure argument in a Terraform provisioner control?

easy

A. It controls what happens if the provisioner script or command fails.

B. It sets the timeout duration for the provisioner execution.

C. It defines the order in which provisioners run.

D. It specifies the operating system for the provisioner.

Solution

1. Step 1: Understand provisioner purpose

   Provisioners run scripts or commands after resource creation.

2. Step 2: Role of on_failure

   The on_failure argument controls what Terraform does if the provisioner fails.

3. Final Answer:

   It controls what happens if the provisioner script or command fails. -> Option A

4. Quick Check:

   on_failure controls failure behavior [OK]

Hint: Remember: on_failure decides action on provisioner failure [OK]

Common Mistakes:

• Confusing on_failure with timeout settings
• Thinking on_failure sets provisioner order
• Assuming on_failure defines OS type

2.

Which of the following is the correct syntax to make a provisioner continue even if it fails?

provisioner "local-exec" {
  command = "echo Hello"
  on_failure = ?
}

easy

A. "continue"

B. "fail"

C. "ignore"

D. "skip"

Solution

1. Step 1: Recall valid on_failure values

   Terraform supports fail and continue as valid on_failure values.

2. Step 2: Identify correct value to continue on failure

   To continue even if the provisioner fails, use continue.

3. Final Answer:

   "continue" -> Option A

4. Quick Check:

   on_failure = "continue" continues on failure [OK]

Hint: Use "continue" to ignore failure and proceed [OK]

Common Mistakes:

• Using invalid values like "ignore" or "skip"
• Confusing "fail" with continuing on failure
• Omitting quotes around the value

3.

Given this Terraform snippet, what happens if the local-exec provisioner command fails?

resource "null_resource" "example" {
  provisioner "local-exec" {
    command = "exit 1"
    on_failure = "fail"
  }
}

medium

A. Terraform retries the provisioner command automatically.

B. Terraform ignores the failure and continues applying other resources.

C. Terraform stops and reports an error, halting the apply process.

D. Terraform logs a warning but marks the resource as created.

Solution

1. Step 1: Analyze provisioner command and on_failure

   The command "exit 1" will fail. The on_failure is set to "fail".

2. Step 2: Understand effect of on_failure = "fail"

   This setting causes Terraform to stop and report an error if the provisioner fails.

3. Final Answer:

   Terraform stops and reports an error, halting the apply process. -> Option C

4. Quick Check:

   on_failure = "fail" stops on failure [OK]

Hint: Fail stops Terraform; continue lets it proceed [OK]

Common Mistakes:

• Assuming Terraform retries automatically
• Thinking failure is ignored with "fail"
• Believing resource is created despite failure

4.

Identify the error in this provisioner block that causes Terraform to ignore failures unexpectedly:

provisioner "remote-exec" {
  inline = ["false_command"]
  on_failure = fail
}

medium

A. The on_failure argument is not allowed in provisioners.

B. The on_failure value should be a string with quotes.

C. The provisioner type remote-exec is not supported.

D. The inline command is invalid and causes syntax error.

Solution

1. Step 1: Check on_failure syntax

   The value for on_failure must be a quoted string, e.g., "fail" or "continue".

2. Step 2: Identify impact of missing quotes

   Without quotes, Terraform treats it as an identifier, causing unexpected behavior or ignoring the setting.

3. Final Answer:

   The on_failure value should be a string with quotes. -> Option B

4. Quick Check:

   on_failure values require quotes [OK]

Hint: Always quote on_failure values "fail" or "continue" [OK]

Common Mistakes:

• Omitting quotes around on_failure values
• Confusing command errors with syntax errors
• Thinking on_failure is unsupported

5.

You want to run a local-exec provisioner that might fail but should not stop Terraform from creating other resources. Which configuration achieves this?

resource "null_resource" "example" {
  provisioner "local-exec" {
    command = "some_command"
    on_failure = ?
  }
}

hard

A. "fail" to stop on failure

B. "retry" to try again on failure

C. "ignore" to silently skip failure

D. "continue" to ignore failure and proceed

Solution

1. Step 1: Understand requirement to not stop Terraform

   The provisioner may fail but Terraform should continue creating other resources.

2. Step 2: Choose correct on_failure value

   Using on_failure = "continue" tells Terraform to ignore provisioner failure and proceed.

3. Final Answer:

   "continue" to ignore failure and proceed -> Option D

4. Quick Check:

   on_failure = "continue" allows continuation on failure [OK]

Hint: Use "continue" to keep going despite provisioner failure [OK]

Common Mistakes:

• Using unsupported values like "retry" or "ignore"
• Choosing "fail" which stops Terraform
• Not quoting the on_failure value