Patterns for infrastructure-as-code
summary
Describes common design patterns for writing infrastructure-as-code with configuration management tools such as Puppet, Ansible and Chef, focusing on using their provided abstractions, extension points and modules instead of treating them as simple file-copying utilities. Presents a catalog of recurring patterns and ready-made abstractions that help express architectural intent and make provisioning code more repeatable and communicative.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:26Images
- 8:58Secrets
- 12:51Code organization
- 25:35Code Quality
- 28:53Side effects
- 36:40Conclusion
- 37:40Questions?
related talks
54mInfrastructure as code (anti) Patterns
46mImplementing Infrastructure as Code
39mRethinking the Approach to Infrastructure as Code
42mInfrastructure as Code - Lessons learned from Dev to Ops
46mThink of your infrastructure as code
32mCode Quality and Infrastructure as Code
21mPitfalls of Infrastructure as Code (And how to avoid them!)
01h 02mTools and Techniques for Infrastructure as Code