I Can’t Do This With Terraform, Now What?
summary
Shows how Terraform remains usable when a resource property is missing, focusing on Azure API Management attaching to a virtual network which Terraform initially lacks support for, then adding the property to the Azure provider and proving it works. Compares practical options: local-exec escape hatch (taint and no state ID), the community shell provider (CRUD scripts exchanging JSON), authoring a tiny Go provider change (add one schema field and wire CRUD), and embedding ARM templates. Provides a GitHub repo of patterns and gotchas for each approach.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 0:14Terraform limitations
- 3:18General purpose tools
- 7:29Local exec usage
- 9:15Shell provider
- 14:25Custom provider development
- 20:03Templating and conclusion
related talks
54mInfrastructure as Code with Terraform on Azure
50mInfrastructure as Code with Terraform - The Fundamentals
45mRETEX: Pitfalls and Traps with Terraform in the Enterprise
35mWhat’s new in Terraform for Azure?
29mTerraform on Azure for Beginners
50mInfrastructure as Code for Azure with Terraform
35mMisadventures with Terraform
29mProper Terraform Authentication for Azure Deployments