Applied
Engineering
Results
samuel-torres.com
Provisioning Azure infrastructure declaratively instead of clicking through the Azure Portal, so environments are reproducible and reviewable — a personal project.
Terraform · Azure · HCL · GitHub Actions · Azure Blob Storage · IaC
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.
terraform plan and terraform apply, so changes go through CI instead of being run ad hoc from a local machine.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.
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.
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.
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.