Ignite: Programming your infrastructure
summary
Argues that infrastructure must be written and tested like an application: code is deployed once successfully with chef cookbooks but fails on repeat runs when scaled, so the real claim is that local development, automated tests and static analysis catch regressions before production. Cites tools like ansible lint, CI and on‑laptop tests, and gives a concrete failure where logstash stopped running after redeploys; notes average job turnover of four years as a reason to make code maintainable.
AI-written summary · about
related talks
05mProgramming your Infrastructure
28mFrom Monitoring to Automated Testing of Your Infrastructure Code
46mImplementing Infrastructure as Code
46mThink of your infrastructure as code
42mInfrastructure as Code - Lessons learned from Dev to Ops
01h 02mTools and Techniques for Infrastructure as Code
06mIgnite: Bryan Liles talks about DevOps
01h 02mTools and Techniques for Infrastructure as Code