Terraform Configuration Language (HCL)

# CHAPTER 3

Terraform Configuration Language (HCL) #

1. Introduction #

2. Learning Objectives #

• Understand the core syntax rules of HCL (HashiCorp Configuration Language).

• Define the structure of a Terraform "Block".

• Differentiate between Block Types, Labels, and Arguments.

• Identify proper string, number, and boolean data types in HCL.

• Write a basic HCL configuration without syntax errors.

3. Beginner-Friendly Explanation #

• The Block Type: "Vehicle" (Tells the factory we are building a car, not a boat).

• The Label: "MyDailyDriver" (A personal nickname so you can refer to it later).

• The Arguments:

• Color = "Red"

• Doors = 4

• Electric = true

In HCL, that exact form looks like this:

vehicle "car" "my_daily_driver" {
  color    = "red"
  doors    = 4
  electric = true
}

You are simply filling out standardized forms telling the cloud exactly what you want.

4. Anatomy of a Terraform Block #

Here is a real AWS server block:

resource "aws_instance" "web_server" {
  ami           = "ami-0c55b159cbfafe1f0"
  instance_type = "t2.micro"
}

Let's break it down:

1. 1. Block Type (resource): The first word. It tells Terraform what *kind* of block this is. A resource block creates infrastructure. A variable block takes input. An output block prints data.

1. 2. Resource Type ("awsinstance"): The first label. This is strictly defined by the Provider (AWS). You cannot make this up. It specifically means "AWS EC2 Virtual Machine."

1. 3. Resource Name ("webserver"): The second label. This is your personal identifier. You can name it "database", "frontend", or "steve". This name is only used *inside* your Terraform code to reference the block.

1. 4. Arguments (ami = ...): The key-value pairs inside the curly braces { }. These are the settings for the resource.

5. HCL Data Types #

• Strings: Must be enclosed in double quotes. "t2.micro"

• Numbers: No quotes. port = 80

• Booleans: true or false (No quotes). encrypted = true

• Lists (Arrays): Enclosed in brackets. security_groups = ["sg-123", "sg-456"]

• Maps (Dictionaries): Enclosed in curly braces with colons or equals signs.

  tags = {
    Name        = "MyServer"
    Environment = "Production"
  }

6. Mini Project: Create First Terraform Configuration #

Step-by-Step Walkthrough:

1. 1. In your project directory, open main.tf.

1. 2. Paste the following HCL code:

# This configures the 'local' provider
terraform {
  required_providers {
    local = {
      source = "hashicorp/local"
      version = "2.4.0"
    }
  }
}

# The Block Type is 'resource'
# The Resource Type is 'local_file'
# The Resource Name is 'hello_document'
resource "local_file" "hello_document" {
  filename = "hello_world.txt"
  content  = "Welcome to Infrastructure as Code! This file was created by a robot."
}

1. 3. Open your terminal and run terraform init (to download the local plugin).

1. 4. Run terraform apply. Type yes when prompted.

1. 5. Observation: Look at your directory! A new file named helloworld.txt has magically appeared, containing your message. You just provisioned infrastructure!

1. 1. Identify the Block Type, Resource Type, and Resource Name in this line: resource "awss3bucket" "mystorage" {

1. 2. Run terraform fmt on a messy HCL file and observe how it standardizes the indentation.

12. FAQs #

13. Interview Questions #

• Q: Break down the anatomical structure of a Terraform HCL configuration block. Explain the difference between the Resource Type and the Resource Name.

• Q: What is the purpose of the terraform fmt command, and why should it be integrated into a team's CI/CD or pre-commit workflow?

14. Summary #

15. Next Chapter Recommendation #