openskills.info
Course catalog
Terraform Fundamentals logoCourse Preview

Terraform Fundamentals

Terraform is a tool for describing and managing infrastructure through configuration files. It compares those files with existing systems, proposes changes, and uses provider plugins to create, update, or remove resources through their APIs.

itInfrastructure and operations

Don't Panic: Terraform Fundamentals

Terraform is a way to describe infrastructure in files and ask a program to compare that description with the objects that actually exist. Before this, someone tended to perform a sequence of API calls, console clicks, and carefully preserved folklore. That can work. So can carrying water in a sieve, if the journey is short enough.

The useful mental model has three parts. Configuration says what resources and relationships are intended. State remembers which Terraform resource address belongs to which remote object. Providers are the plugins that read and change those remote objects through platform APIs. Terraform compares all three and writes a plan, which is a proposal rather than a small army of commands escaping into production.

The surprising part is state. It is not a receipt that can be discarded after a successful apply. It contains the bindings Terraform needs to recognize existing infrastructure. A shared remote backend gives a team one record of those bindings and can lock an operation, but state and saved plans can contain sensitive values. They deserve the same care as other operational data, although the filename may look disappointingly harmless.

The working rhythm is pleasantly repetitive: write, initialize, plan, review, apply. Initialization installs required providers and modules and prepares the backend. A plan can create, update, replace, or destroy objects. terraform validate checks syntax and internal consistency, but it does not inspect a remote service or declare a replacement wise. The plan is where the awkward questions live, so read it before asking apply to become very efficient.

Terraform works best for lasting objects exposed by a suitable provider and API. It is less useful for a one-time procedure with no managed object. Start with the disposable Docker example, where a container can be built, changed, and destroyed without opening a cloud account. Then move to the Cheatsheet for the compact map of blocks, state, and plan actions; the Practice tab for the command cycle; and the Timeline and Landscape tabs when the basic loop starts to look like a larger operating system.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources