Why modules enable reusability in Terraform - Visual Breakdown

Process Flow - Why modules enable reusability

Write module code once

↓

Save module as reusable unit

↓

Call module multiple times

↓

Each call creates resources

↓

Manage infrastructure easily

Modules let you write code once and use it many times, making infrastructure easier to manage and reuse.

Execution Sample

Terraform

module "network1" {
  source = "./modules/network"
  cidr_block = "10.0.0.0/16"
}

module "network2" {
  source = "./modules/network"
  cidr_block = "10.1.0.0/16"
}

This code calls the same network module twice with different settings to create two networks.

Process Table

Step	Action	Module Called	Input Variables	Resources Created
1	Start Terraform apply	-	-	-
2	Call module 'network1' first time	network1	cidr_block=10.0.0.0/16	VPC with 10.0.0.0/16
3	Call module 'network2' second time	network2	cidr_block=10.1.0.0/16	VPC with 10.1.0.0/16
4	Finish apply	-	-	Two separate VPCs created
5	Exit	No more modules to call	-	-

💡 All module calls completed, infrastructure created as per inputs

Status Tracker

Variable	Start	After 1	After 2	Final
cidr_block	undefined	10.0.0.0/16	10.1.0.0/16	10.1.0.0/16
resources_created	none	VPC with 10.0.0.0/16	VPC with 10.1.0.0/16	Two VPCs total

Key Moments - 2 Insights

Why can we use the same module multiple times with different inputs?

Because each module call is independent and uses its own input variables, as shown in steps 2 and 3 of the execution_table.

Does writing a module once mean it creates only one resource?

No, each time you call the module it creates resources separately, so multiple calls create multiple resources (see steps 2 and 3).

Visual Quiz - 3 Questions

Look at the execution_table, what is the cidr_block input for the second module call?

A 10.0.0.0/16

B 10.1.0.0/16

C undefined

D 10.2.0.0/16

💡 Hint

Check row 3 under Input Variables in the execution_table

At which step does Terraform finish creating all resources?

A Step 4

B Step 3

C Step 2

D Step 5

💡 Hint

Look at the Resources Created column in step 4 of the execution_table

If we change the cidr_block in the first module call, what changes in the variable_tracker?

A Final value for cidr_block changes to the new first call value

B After 2 value for cidr_block changes

C Only After 1 value for cidr_block changes

D No changes happen

💡 Hint

See how cidr_block changes after each module call in variable_tracker

Concept Snapshot

Modules let you write infrastructure code once and reuse it many times.
Each module call can have different inputs.
Each call creates separate resources.
This saves time and reduces errors.
Modules help organize and scale infrastructure easily.

Full Transcript

Modules in Terraform are reusable units of infrastructure code. You write the module once and then call it multiple times with different inputs. Each call creates its own resources based on the inputs provided. This means you can manage similar infrastructure components easily without repeating code. The execution trace shows two calls to the same network module with different CIDR blocks, resulting in two separate virtual networks. Variables track the inputs and resources created at each step. This approach improves efficiency and organization in cloud infrastructure management.