625 saved links — infrastructure written down instead of clicked into existence. This is the tooling of your 2014–2023 chapter (Terraform and Bicep, heavily Azure-flavoured), and the corpus now documents the next shift: agents writing and operating the infrastructure code themselves.
Related: DevOps · Azure · GitOps · Platform Engineering
Start here
- Gruntwork’s Terraform crash course — learn by doing, in minutes.
- terraform-best-practices.com and Awesome Terraform — the largest curated collection.
- Nathan Peck: rethinking infrastructure as code from scratch — the best zoom-out.
- “Infrastructure as Code is dead — long live Infrastructure from Code” and Hohpe’s IxC: as code, from code, with code — where the abstraction is heading.
- the IaC landscape overview.
Terraform craft
- Structure: the environment + application design pattern · components of a modern Terraform stack · managing multiple environments with environment-specific directories · Terragrunt for multi-environment management.
- State: mastering state management and the state tree · best practices for state files in CI/CD · handling .terraform.lock.hcl without pain.
- Modules: module best practices · a practical module guide · auto-releasing modules in a mono-repo.
- Importing what already exists: Terraform import · import blocks for Azure resources.
- At scale on Azure: recommended configs for Terraform + GitHub Actions at scale · multi-environment projects without losing your mind · Azure Verified Modules with Terraform · not blocking Terraform with Azure resource locks · the full Azure course (video).
Testing & cost control
The two disciplines that separate IaC from IaC-that-you-trust.
- Terraform 1.6’s native testing framework (InfoQ’s take) · the walkthrough (video) · meaningful tests with Terratest.
- scanning the Terraform plan with Trivy — catch misconfigurations before apply; also IaC vulnerability scanning.
- Infracost — cloud cost breakdowns in every pull request with the Azure DevOps integration.
- Atlantis — Terraform pull-request automation.
The Bicep corner
Your Azure-native second language — one of the deepest personal clusters in the vault.
- John Lokerse’s Azure Bicep cheat sheet — the quick reference; plus 7 practical Bicep tips.
- Language depth: user-defined types changed Bicep best practice · reusability with user-defined data types · what actually happens when a Bicep template deploys.
- Quality gates: the Bicep lint command, scripted into the pipeline · testing and approving Bicep with GitHub Actions (video).
- Deployment stacks: automating Bicep with Deployment Stacks · deploying a landing zone with stacks + Bicep · Bicep For Real on stacks (video, from bicepforreal.com).
- Ecosystem: Azure/ResourceModules — mature curated Bicep modules with a CI platform · the awesome-Bicep community repo · Fabric 101: deploy capacity with ARM, Bicep, and Terraform.
- The frontier: Agent Skills for automating repeatable Bicep workflows with Copilot — your two worlds meeting.
Beyond Terraform
- Pulumi vs. Terraform, compared properly · what Pulumi ESC actually is · “the real AI challenge is cloud, not code”.
- Crossplane 101 for Terraform people and migrating Terraform state to Crossplane.
- Awesome Ansible · using Terraform and Ansible together.
- Winglang — a potential game-changer? · Radius: cloud-agnostic app definitions in Bicep, deployable to AWS and Azure.
- when to use Terraform — and when not to.
IaC meets AI
- GenAI for generating, interpreting, and debugging IaC and evaluating LLM-generated IaC — trust, but verify.
- the Terraform MCP server (announced as the Azure provider crossed 1B downloads).
- Pulumi Neo — an AI agent for infra engineers, not devs.
- CAIRA: a composable IaC baseline for secure, observable AI infrastructure · running Claude on Microsoft Foundry with your existing IaC.
- GitHub Copilot for Terraform, hands-on · AI-assisted IaC for beginners.