How to write cloud-agnostic Terraform code
summary
Claims that Terraform 0.12/0.13 suffices to write provider‑agnostic modules and demonstrates it by provisioning three VMs across AWS and Azure from one codebase; uses Terraform 0.13 provider forwarding and count on modules to instantiate provider‑specific submodules, maps abstract inputs to provider tables, relies on object variables with validation and data sources for decoupling, and keeps provider configs per module. Sample repo is on GitHub and the demo successfully creates the expected EC2 and Azure VM resources.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 2:50Concept and motivation
- 6:25Provider comparison
- 8:58Architectural approach
- 14:16Technical implementation
- 25:33Live demo
- 29:42Summary and resources
- 32:45Q&A session
related talks
48mCodifying Infrastructure with Terraform for the Future
46mTerraform best practices with examples and arguments
46mTerraform best practices with examples and arguments
34mTerraform: A Novel About Modules, Providers, Security, and Pain
23mWhen Infrastructure as Code Ends: Creating Terraform Providers
33mBuilding applications with infrastructure as code
43mDemystifying Terraform - "Hardcore" to Core Infrastructure... Tool
30mVersions: Terraform, Providers, & Modules; Oh My!