File naming conventions (.tf files) in Terraform - Step-by-Step Execution

Process Flow - File naming conventions (.tf files)

Start Terraform Project

↓

Create .tf files

↓

Name files by purpose

↓

Terraform loads all .tf files

↓

Apply configuration

↓

End

Terraform reads all .tf files in a folder. Naming files by purpose helps organize and understand the project.

Execution Sample

Terraform

main.tf
variables.tf
outputs.tf
network.tf
security.tf

Example of common Terraform file names showing how to separate configuration by purpose.

Process Table

Step	Action	File Name	Purpose	Effect
1	Create main configuration file	main.tf	Defines main resources	Terraform loads main resources
2	Create variables file	variables.tf	Defines input variables	Terraform knows inputs to expect
3	Create outputs file	outputs.tf	Defines outputs	Terraform knows what to show after apply
4	Create network config file	network.tf	Defines network resources	Network setup separated for clarity
5	Create security config file	security.tf	Defines security groups and rules	Security setup separated for clarity
6	Terraform loads all .tf files	All .tf files	Combined configuration	Terraform merges all configs before apply
7	Apply terraform	N/A	Execute plan	Infrastructure created as defined
8	End	N/A	Complete	Project deployed successfully

💡 All .tf files loaded and merged; terraform apply completes deployment

Status Tracker

File	Created	Purpose Defined	Loaded by Terraform
main.tf	Yes	Yes	Yes
variables.tf	Yes	Yes	Yes
outputs.tf	Yes	Yes	Yes
network.tf	Yes	Yes	Yes
security.tf	Yes	Yes	Yes

Key Moments - 3 Insights

Why do we split Terraform configuration into multiple .tf files?

Splitting files by purpose (see execution_table steps 1-5) helps organize code, making it easier to read and maintain.

Does Terraform care about the order or names of .tf files?

No, Terraform loads all .tf files in the folder together regardless of name or order (see execution_table step 6).

Can we name .tf files anything we want?

Yes, but using descriptive names like variables.tf or network.tf helps others understand the project quickly (see execution_table steps 2 and 4).

Visual Quiz - 3 Questions

Look at the execution_table, which file defines input variables?

A variables.tf

B main.tf

C outputs.tf

D network.tf

💡 Hint

Check the Purpose column in execution_table row 2

At which step does Terraform load all .tf files together?

A Step 3

B Step 5

C Step 6

D Step 7

💡 Hint

Look for 'Terraform loads all .tf files' in execution_table

If we add a file named database.tf, what will happen during terraform apply?

A Terraform ignores database.tf

B Terraform loads database.tf and merges its config

C Terraform errors because of unknown file

D Terraform only loads main.tf and variables.tf

💡 Hint

Refer to execution_table step 6 about loading all .tf files

Concept Snapshot

Terraform reads all .tf files in a folder together.
Name files by purpose: main.tf, variables.tf, outputs.tf, etc.
File order and names do not affect loading.
Organizing files improves readability and maintenance.
Add new .tf files anytime; Terraform merges all configs.

Full Transcript

Terraform projects use multiple .tf files to organize infrastructure code. Each file has a purpose, like main.tf for main resources, variables.tf for inputs, and outputs.tf for outputs. Terraform loads all .tf files in the folder together, regardless of their names or order. This means you can split your configuration into logical parts for clarity. When you run terraform apply, it merges all these files and applies the combined configuration. Naming files clearly helps you and others understand the project structure easily.