Module inputs (variables) in Terraform - Time & Space Complexity

Time Complexity: Module inputs (variables)

O(n)

Understanding Time Complexity

We want to understand how the time to apply Terraform changes grows when we use module inputs (variables).

Specifically, how does the number of inputs affect the work Terraform does?

Scenario Under Consideration

Analyze the time complexity of passing multiple variables into a Terraform module.

module "example" {
  source = "./modules/example"

  var1 = var.input1
  var2 = var.input2
  var3 = var.input3
  # ... imagine many more variables
}

This code passes several input variables into a module to configure resources inside it.

Identify Repeating Operations

Look at what repeats as the number of inputs grows.

• Primary operation: Terraform reads and processes each input variable to pass into the module.
• How many times: Once per input variable.

How Execution Grows With Input

As you add more input variables, Terraform does more work reading and validating them.

Input Size (n)	Approx. Operations
10	10 variable reads and validations
100	100 variable reads and validations
1000	1000 variable reads and validations

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

Final Time Complexity

Time Complexity: O(n)

This means the time to process inputs grows in a straight line as you add more variables.

Common Mistake

[X] Wrong: "Adding more variables won't affect Terraform's processing time much."

[OK] Correct: Each variable requires reading and validation, so more variables mean more work.

Interview Connect

Understanding how input size affects processing helps you design efficient modules and predict deployment times.

Self-Check

"What if we changed from many individual variables to a single map variable? How would the time complexity change?"

Practice

1. What is the main purpose of using variables in a Terraform module?

easy

A. To customize module behavior without changing its code

B. To store sensitive data only

C. To define output values from the module

D. To create resources automatically

Solution

1. Step 1: Understand module customization

   Variables allow users to provide input values to modules, changing how they behave without editing the module code itself.

2. Step 2: Differentiate variables from other features

   Variables are not for outputs or automatic resource creation; they are inputs to customize modules.

3. Final Answer:

   To customize module behavior without changing its code -> Option A

4. Quick Check:

   Module inputs = customization [OK]

Hint: Variables customize modules without code edits [OK]

Common Mistakes:

• Confusing variables with outputs
• Thinking variables create resources
• Assuming variables only store secrets

2. Which of the following is the correct syntax to declare a string variable named region with a default value of us-west-1?

easy

A. variable "region" = "us-west-1"

B. variable region { type = "string" default = us-west-1 }

C. variable "region" { default = us-west-1 type = string }

D. variable "region" { type = string default = "us-west-1" }

Solution

1. Step 1: Check variable block syntax

   Terraform variables use the syntax: variable "name" { type = string default = "value" } with quotes around strings.

2. Step 2: Validate variable "region" { type = string default = "us-west-1" }

   correctly uses quotes for the variable name and default string value, and sets type properly.

3. Final Answer:

   variable "region" { type = string default = "us-west-1" } -> Option D

4. Quick Check:

   Correct variable block syntax = variable "region" { type = string default = "us-west-1" } [OK]

Hint: Use quotes for names and string defaults in variable blocks [OK]

Common Mistakes:

• Missing quotes around strings
• Wrong order of attributes
• Assigning variable directly without block

3. Given this module variable declaration:

variable "instance_count" {
  type    = number
  default = 2
}

And this usage inside the module:

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

What will happen if the module is called without specifying instance_count?

medium

A. Only one instance will be created

B. Two AWS instances will be created

C. An error occurs because instance_count is missing

D. No instances will be created

Solution

1. Step 1: Understand default variable behavior

   If a variable has a default value and is not overridden, Terraform uses the default.

2. Step 2: Apply default to resource count

   The count argument uses var.instance_count, which defaults to 2, so two instances are created.

3. Final Answer:

   Two AWS instances will be created -> Option B

4. Quick Check:

   Default variable value used = 2 instances [OK]

Hint: Default variable values apply if no input given [OK]

Common Mistakes:

• Assuming missing variable causes error
• Thinking default is ignored
• Confusing count with instance_type

4. You have this variable declaration inside a module:

variable "env" {
  type = string
}

When calling the module, you forget to provide a value for env. What will happen?

medium

A. Terraform will throw an error about missing required variable

B. Terraform will use an empty string as default

C. Terraform will assign null automatically

D. Terraform will use the string "env" as default

Solution

1. Step 1: Check variable declaration for default

   The variable env has no default value, so it is required.

2. Step 2: Understand Terraform behavior on missing required variables

   If a required variable is not provided, Terraform throws an error and stops.

3. Final Answer:

   Terraform will throw an error about missing required variable -> Option A

4. Quick Check:

   Required variable missing = error [OK]

Hint: No default means variable is required [OK]

Common Mistakes:

• Assuming empty string or null is automatic default
• Thinking Terraform guesses a value
• Confusing variable name with default

5. You want to create a reusable module that accepts a list of subnet IDs as input. Which variable declaration correctly enforces that the input must be a list of strings and has no default value?

hard

A. variable "subnet_ids" { type = string default = [] }

B. variable "subnet_ids" { type = list number default = ["subnet-123"] }

C. variable "subnet_ids" { type = list(string) }

D. variable "subnet_ids" { type = list(string) default = null }

Solution

1. Step 1: Identify correct type syntax for list of strings

   Terraform uses list(string) to specify a list where each item is a string.

2. Step 2: Check default value presence

   No default means the variable is required. variable "subnet_ids" { type = list(string) } has no default, so input must be provided.

3. Final Answer:

   variable "subnet_ids" { type = list(string) } -> Option C

4. Quick Check:

   List of strings required, no default = variable "subnet_ids" { type = list(string) } [OK]

Hint: Use type = list(string) and omit default to require input [OK]

Common Mistakes:

• Using wrong type like string instead of list(string)
• Providing default empty list when input should be required
• Using invalid syntax for type or default