More
Сhoose

Applied

Engineering

Results

samuel-torres.com

Mexico City

Mexico City, Mexico Available immediately

Availability

Remote and on-site projects MXN · USD

Azure Infrastructure as Code — Terraform

Read about the project
Dark server rack hardware with status LEDs, representing cloud infrastructure
Terraform · IaC · Azure
2026
Role

Provisioning Azure infrastructure declaratively instead of clicking through the Azure Portal, so environments are reproducible and reviewable — a personal project.

Core stack

Terraform · Azure · HCL · GitHub Actions · Azure Blob Storage · IaC

Code

View on GitHub →

What it is

Provisioning Azure infrastructure the same way application code is written: as version-controlled, reviewable files, instead of a sequence of manual clicks in the Azure Portal that nobody can diff or replay. The resource definitions live in HCL, and a CI pipeline is the only thing that actually applies them.

How it's built

  • Azure resources defined in HCL, with variables separated from resource definitions so the same configuration can target different environments.
  • Remote state stored in Azure Blob Storage rather than kept as a local file — state that only lives on one laptop can't be shared or trusted.
  • A GitHub Actions workflow running terraform plan and terraform apply, so changes go through CI instead of being run ad hoc from a local machine.
  • The full init → plan → apply → destroy cycle exercised deliberately, including tearing environments down cleanly instead of only ever building them up.

Design notes

Plan is reviewed before apply, never applied blind

+
-

Terraform's plan output is the whole point — it says exactly what will change before anything actually changes. Applying without reading the plan defeats the reason to use Terraform at all.

Remote state, not a local file

+
-

State stored in Azure Blob Storage means the source of truth about what's deployed isn't tied to one machine, and supports locking so two applies can't collide.

CI is the only thing that applies

+
-

Running apply from GitHub Actions instead of a local terminal means every change to real infrastructure has a matching commit and a log of what ran.

Short version (portfolio card)

Azure infrastructure provisioned as code with Terraform: HCL resource definitions, remote state on Azure Blob Storage, and plan/apply run through a GitHub Actions pipeline.

Resume / LinkedIn bullets

  • Provisioned Azure infrastructure as code with Terraform (HCL), replacing manual Azure Portal setup with reviewable, version-controlled configuration.
  • Configured remote Terraform state on Azure Blob Storage for shared, lockable state instead of a local state file.
  • Automated plan/apply through a GitHub Actions CI pipeline.
I work with national and international clients. Rates in USD and MXN.

Have a project that needs an engineer who delivers?

Professional contact:

Mexico City

Mexico City, Mexico Available immediately

Availability

Remote and on-site projects MXN · USD

© 2026 Eng. Samuel Torres. Applied Engineering.

Versión en español