Terraform Explained: Infrastructure as Code Fundamentals

The Terraform Workflow at a Glance

Terraform reads your configuration, compares it with its state and the real platform, then shows a plan. The important habit is review: treat the plan as a change proposal, not a formality.

Terraform Concepts in Simple Words

Terraform files use HashiCorp Configuration Language, usually called HCL. It looks a little like JSON, but is designed to be easy to read and reuse.

Alternatives: OpenTofu uses a very similar workflow. Pulumi uses general-purpose programming languages. Tools such as Ansible are usually better for configuring and checking existing devices after infrastructure is ready.

What Terraform Is

Terraform is an Infrastructure as Code tool. You write the desired infrastructure in human-readable configuration files. A provider translates that description into API calls for a platform such as a cloud service, DNS platform, IPAM system or network controller.

This is different from a script that only lists commands in order. Terraform still needs careful thinking, but it gives the team a clearer before-and-after view.

The Core Terraform Parts

resource "example_network" "training" {
  name     = "training-network"
  location = var.location
}

The example is deliberately simple. Real resource names and fields come from the provider documentation for the platform you manage.

Why State, Plan and Review Matter

Terraform state records the relationship between your configuration and real infrastructure. It lets Terraform calculate whether an object should be created, changed or removed. Because it can contain sensitive information, keep it protected and use a shared remote backend for team work.

1. InitializeDownload and configure the providers and backend needed for the project.
2. Validate and formatCatch basic mistakes before requesting a platform change.
3. PlanRead the proposed change carefully, especially replacements and deletions.
4. ApplyMake the reviewed change, then verify the real service and update the record.

Terraform with Cisco IOS XE and RESTCONF

Terraform can also manage supported network devices. In this example, the IOS XE provider reads your HCL file, sends API requests over HTTPS RESTCONF, and creates a loopback interface on the router.

terraform {
  required_providers {
    iosxe = { source = "CiscoDevNet/iosxe" }
  }
}

resource "iosxe_interface_loopback" "training" {
  name              = 100
  description       = "Terraform training loopback"
  shutdown          = false
  ipv4_address      = "1.1.1.1"
  ipv4_address_mask = "255.255.255.255"
}

This small example describes one loopback interface. Before using it, configure RESTCONF and HTTPS on a lab router, follow the provider documentation for your supported IOS XE release, and keep the router URL and login details outside the code.

• Provision cloud virtual networks, subnets, route tables, gateways and security rules.
• Create repeatable environments for labs, application teams or branch deployments.
• Manage API-driven network services alongside compute and application infrastructure.
• Keep reviewed infrastructure definitions in Git with a clear history of why a change happened.

The Final Lesson: Ansible

Terraform is often strongest when you need to create or manage infrastructure objects through an API. Ansible is commonly used to configure and validate many existing network devices. Together, they support a practical automation workflow.

Terraform Explained: Infrastructure as Code Fundamentals Frequently Asked Questions