How to Build a Usable Terraform Provider in 20 hours
summary
Built live on Twitch over 10 two-hour sessions, a usable Terraform provider for Fire Hydrant reaches working status in about 20 hours and publishes to the Terraform registry with six resource types and matching data sources. Code uses Go, accepts that you will type interface a lot, and benefits from copying early, mapping provider schema to the API, and switching to Terraform acceptance tests. Documentation is generated with tf plugin docs, leaving examples and gotchas for manual polishing.
AI-written summary · about
chapters (13)
- 0:00Introduction to talk
- 1:45Live stream build process
- 3:56Challenges faced building
- 5:24Don’t over-abstract schemas
- 8:11API schema must match provider
- 9:36Embrace acceptance tests early
- 12:28Expect many interface uses
- 13:51Learn from large providers
- 15:37Auto-generate docs with tf plugin docs
- 17:27Terraform conventions mastery
- 18:31Start with simplest resources
- 20:57Final results and insights
- 22:20Q&A and closing
related talks
01h 04mBuild your own Terraform provider
23mWhen Infrastructure as Code Ends: Creating Terraform Providers
49mLet's dive into Terraform provider creation
26mEverything as Code with Terraform
48mCodifying Infrastructure with Terraform for the Future
34mTerraform: A Novel About Modules, Providers, Security, and Pain
46mTerraform best practices with examples and arguments
46mTerraform best practices with examples and arguments