Terraform file organization - Step-by-Step Execution

Process Flow - Terraform file organization

Start: Create main.tf

↓

Define provider and resources

↓

Create variables.tf

↓

Declare input variables

↓

Create outputs.tf

↓

Declare outputs

↓

Optional: Create terraform.tfvars

↓

Assign variable values

↓

Run terraform init & apply

↓

Infrastructure deployed

↓

End

Terraform files are organized by purpose: main.tf for resources, variables.tf for inputs, outputs.tf for outputs, and optional terraform.tfvars for variable values. This flow shows how these files work together to deploy infrastructure.

Execution Sample

Terraform

provider "aws" {
  region = var.region
}

resource "aws_s3_bucket" "bucket" {
  bucket = var.bucket_name
}

Defines AWS provider and an S3 bucket resource using variables for region and bucket name.

Process Table

Step	File Processed	Action	Effect	Next Step
1	main.tf	Read provider and resource blocks	Provider and resource defined with variable references	Process variables.tf
2	variables.tf	Read variable declarations	Variables region and bucket_name declared	Process outputs.tf
3	outputs.tf	Read output declarations	Outputs defined for resource attributes	Check terraform.tfvars (optional)
4	terraform.tfvars	Read variable values	Variables assigned actual values	Run terraform init
5	terraform init	Initialize working directory	Plugins downloaded, backend configured	Run terraform apply
6	terraform apply	Apply configuration	Infrastructure created with given variables	End
7	-	End	Infrastructure deployed successfully	-

💡 All files processed and terraform commands run to deploy infrastructure.

Status Tracker

Variable	Declared	Assigned in terraform.tfvars	Used in main.tf	Final Value
region	Declared as string	"us-east-1"	Used in provider block	us-east-1
bucket_name	Declared as string	"my-unique-bucket"	Used in resource bucket name	my-unique-bucket

Key Moments - 3 Insights

Why do we separate variables into variables.tf instead of putting them directly in main.tf?

Separating variables in variables.tf keeps main.tf focused on resources and makes it easier to manage inputs separately, as shown in execution_table steps 1 and 2.

What happens if terraform.tfvars is missing?

Terraform uses default variable values or prompts for input. Without terraform.tfvars (step 4), variables may be undefined causing errors or manual input.

Why do we have outputs.tf as a separate file?

Outputs.tf organizes outputs separately for clarity and reuse, as seen in step 3, making it easier to find what information Terraform will show after apply.

Visual Quiz - 3 Questions

Look at the execution_table, at which step are variable values assigned?

A Step 4

B Step 2

C Step 5

D Step 6

💡 Hint

Check the 'Action' column for 'Read variable values' in execution_table.

According to variable_tracker, what is the final value of 'bucket_name'?

A us-east-1

B Undefined

C my-unique-bucket

D bucket_name

💡 Hint

Look at the 'Final Value' column for 'bucket_name' in variable_tracker.

If we remove outputs.tf, what impact is shown in the execution flow?

A Terraform apply will fail at step 6

B Outputs will not be declared or shown after apply

C Variables will not be assigned

D Provider will not initialize

💡 Hint

Refer to execution_table step 3 about outputs.tf role.

Concept Snapshot

Terraform files are organized by role:
- main.tf: resources and provider
- variables.tf: input variable declarations
- outputs.tf: output declarations
- terraform.tfvars: variable values
This separation keeps configs clean and manageable.

Full Transcript

Terraform file organization involves splitting configuration into files by their purpose. The main.tf file contains provider and resource definitions, referencing variables declared in variables.tf. Outputs.tf declares outputs to show after deployment. Optionally, terraform.tfvars assigns values to variables. The process starts by reading main.tf, then variables.tf, outputs.tf, and terraform.tfvars if present. Terraform commands init and apply then deploy the infrastructure. Variables track from declaration to assignment and usage. This organization helps keep Terraform projects clear and easy to manage.