Terraform Structure & Enablement
summary
Practical roadmap for Terraform adoption: start from ad hoc TF files (terith), move to local modules and env folders (terramod), then use Terraform Cloud/Enterprise workspaces and a private module registry to get remote state, access controls, cost estimates and Sentinel policies, and optionally push reuse further with a CLI-driven multi-workspace pattern dubbed terrorless. Notes: ~800 providers and >5,000 public modules exist, many teams still use terith (30–40%), and terrorless is rare (~2%) and requires careful CLI orchestration rather than VCS runs.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:40Terraform
- 1:48Technical complexity
- 2:14Organizational complexity
- 4:19Traditional IT
- 7:08Where does Terraform fit
- 7:59Where are you at
- 8:47Infrastructure as Code Space
- 11:25Teralith
- 13:38Infrastructure as Code
- 14:13Terraform Module
- 16:27Terraform Infrastructure
- 16:59Remote Backend
- 19:46Teraless
- 20:41Auto vars
- 22:22Repositories
- 23:24Mono Repo
- 23:52Disadvantages
- 26:13Questions
- 26:54Terraform deployments
related talks
46mTerraform best practices with examples and arguments
46mTerraform best practices with examples and arguments
31mTerraform Practices to Enable Infrastructure Scaling
35mTerraform Practices - The Good, the Bad and the Ugly
06mIGNITE: Terraform Practice to Enable Infrastructure Scaling
48mCodifying Infrastructure with Terraform for the Future
30mTerraform Practices to Enable Infrastructure Scaling
34mTerraform: A Novel About Modules, Providers, Security, and Pain