Root module concept in Terraform - Step-by-Step Execution

Process Flow - Root module concept

Start Terraform Run

↓

Load Root Module

↓

Parse root main.tf

↓

Load child modules if any

↓

Evaluate variables and outputs

↓

Plan and Apply Infrastructure

↓

End

Terraform starts by loading the root module, which is the main folder with configuration files. It then processes any child modules, variables, and outputs before applying changes.

Execution Sample

Terraform

terraform {
  required_version = ">= 1.0"
}

resource "aws_s3_bucket" "example" {
  bucket = "my-example-bucket"
}

This code defines a root module with a single AWS S3 bucket resource.

Process Table

Step	Action	Module Loaded	Resource Processed	Variables Evaluated	Outputs Evaluated
1	Start Terraform run	root	none	none	none
2	Parse root main.tf	root	none	none	none
3	Process resource aws_s3_bucket.example	root	aws_s3_bucket.example	none	none
4	Evaluate variables (none defined)	root	aws_s3_bucket.example	none	none
5	Evaluate outputs (none defined)	root	aws_s3_bucket.example	none	none
6	Plan infrastructure changes	root	aws_s3_bucket.example	none	none
7	Apply infrastructure changes	root	aws_s3_bucket.example	none	none
8	End Terraform run	root	aws_s3_bucket.example	none	none

💡 Terraform finishes after applying all resources defined in the root module.

Status Tracker

Variable	Start	After Step 4	Final
bucket_name	undefined	undefined	undefined

Key Moments - 3 Insights

Why does Terraform start with the root module?

Terraform always begins with the root module because it is the main folder containing the configuration files that define the infrastructure. This is shown in execution_table step 2 where the root main.tf is parsed first.

What happens if there are no variables defined in the root module?

If no variables are defined, Terraform simply skips variable evaluation as seen in execution_table step 4 where variables are 'none'. This means default or no values are used.

How does Terraform handle child modules in the root module?

Terraform loads child modules after parsing the root module. This is implied in the concept flow where after loading the root module, child modules are loaded before planning and applying.

Visual Quiz - 3 Questions

Look at the execution table, at which step is the aws_s3_bucket resource processed?

A Step 3

B Step 2

C Step 5

D Step 7

💡 Hint

Check the 'Resource Processed' column in the execution_table rows.

According to the variable tracker, what is the value of 'bucket_name' after step 4?

A empty string

B undefined

C my-example-bucket

D null

💡 Hint

Look at the 'After Step 4' column for 'bucket_name' in variable_tracker.

If a child module was added, at which point in the concept flow would it be loaded?

A Before starting Terraform run

B After applying infrastructure

C After loading root module

D After evaluating outputs

💡 Hint

Refer to the concept_flow ASCII diagram where child modules load after root module.

Concept Snapshot

Terraform Root Module:
- The root module is the main folder with Terraform files.
- Terraform starts by loading and parsing the root module.
- It processes resources, variables, and outputs here.
- Child modules are loaded after the root module.
- Terraform plans and applies infrastructure from the root module.

Full Transcript

Terraform uses the root module as the starting point for any infrastructure deployment. The root module is simply the folder where your main Terraform configuration files live. When you run Terraform, it first loads this root module, parses the configuration files like main.tf, and processes any resources defined there. If there are child modules referenced, Terraform loads those next. Then it evaluates variables and outputs before planning and applying the infrastructure changes. This flow ensures Terraform knows exactly what to create or change in your cloud environment starting from the root module.

Practice

1. What is the root module in Terraform?

easy

A. A Terraform provider plugin

B. A special Terraform resource type

C. A remote backend configuration

D. The main folder where Terraform commands are run and resources are defined

Solution

1. Step 1: Understand the root module role

   The root module is the main folder where you write your Terraform code and run commands.

2. Step 2: Differentiate from other concepts

   It is not a resource type, backend, or provider plugin but the main working directory.

3. Final Answer:

   The main folder where Terraform commands are run and resources are defined -> Option D

4. Quick Check:

   Root module = main Terraform folder [OK]

Hint: Root module is your main Terraform folder [OK]

Common Mistakes:

• Confusing root module with provider or backend
• Thinking root module is a resource type
• Assuming root module is a plugin

2. Which command must be run inside the root module folder to initialize Terraform?

easy

A. terraform apply

B. terraform init

C. terraform plan

D. terraform validate

Solution

1. Step 1: Identify the initialization command

   terraform init sets up the working directory by downloading providers and preparing the backend.

2. Step 2: Confirm command location

   This command must be run inside the root module folder where the Terraform files exist.

3. Final Answer:

   terraform init -> Option B

4. Quick Check:

   Initialize Terraform = terraform init [OK]

Hint: Use 'terraform init' to start in root module folder [OK]

Common Mistakes:

• Running terraform apply before init
• Confusing init with plan or validate
• Running commands outside root module folder

3. Given this root module folder structure:

root-module/
  main.tf
  variables.tf
  modules/
    network/
      main.tf

Which statement is true about the root module?

medium

A. It can call the network module inside the modules folder

B. It must be empty to work correctly

C. It cannot use modules from subfolders

D. It only contains variables and no resources

Solution

1. Step 1: Understand root module and submodules

   The root module can call other modules located in subfolders like modules/network.

2. Step 2: Evaluate options

   It can call the network module inside the modules folder correctly states the root module can call the network module. Other options are false.

3. Final Answer:

   It can call the network module inside the modules folder -> Option A

4. Quick Check:

   Root module calls submodules = true [OK]

Hint: Root module can call modules in subfolders [OK]

Common Mistakes:

• Thinking root module cannot use submodules
• Assuming root module must be empty
• Believing root module only has variables

4. You run terraform apply in your root module folder but get an error: "No configuration files found". What is the likely cause?

medium

A. You ran the command outside the root module folder

B. You forgot to run terraform init first

C. Your Terraform version is outdated

D. You have no internet connection

Solution

1. Step 1: Analyze the error message

   "No configuration files found" means Terraform cannot find .tf files in the current folder.

2. Step 2: Identify common cause

   This usually happens if you run terraform apply outside the root module folder where the files exist.

3. Final Answer:

   You ran the command outside the root module folder -> Option A

4. Quick Check:

   Run commands inside root module folder [OK]

Hint: Run commands inside root module folder with .tf files [OK]

Common Mistakes:

• Assuming init missing causes this error
• Blaming Terraform version or internet
• Not checking current folder location

5. You want to organize your Terraform project with a root module that calls two child modules: network and compute. Which folder structure and root module code is correct?

hard

A. root/
main.tf
network.tf
compute.tf

# main.tf does not call modules

B. root/
network/
main.tf
compute/
main.tf

# main.tf calls modules from root folder

C. root/
main.tf
modules/
network/
main.tf
compute/
main.tf

# main.tf calls both modules with module blocks

D. root/
main.tf
modules/
network/
main.tf
compute/
main.tf

# main.tf does not call any modules

Solution

1. Step 1: Understand proper module folder structure

   Child modules should be inside a modules folder under root for clarity and best practice.

2. Step 2: Confirm root module calls child modules

   The root module's main.tf must include module blocks to call network and compute modules.

3. Final Answer:

   Folder with modules subfolder and main.tf calling modules -> Option C

4. Quick Check:

   Root calls modules in modules/ folder [OK]

Hint: Put child modules in modules/ and call them in root main.tf [OK]

Common Mistakes:

• Placing modules outside modules/ folder
• Not calling modules in root main.tf
• Confusing separate folders as root module