CLI, CI, DIY: Crafting Python Based Dev Tools in a DevOps Vacuum
summary
A small team replaces a brittle bash monolith with a Python package called Machina, built in about four weeks, that centralizes AWS, ECR, S3, Kafka, GitHub, Jira and Grafana integrations, uses Typer and DDD-style adapters, dynamically loads runnable Python IP files per repo and supports dry‑run and external state storage. Adoption happens in weeks, deployments and QA tasks become faster and more reliable, some legacy features remain missing, and the approach fits small teams without dedicated DevOps.
AI-written summary · about
chapters (6)
- 0:00Introduction and background
- 6:12Why build a new tool
- 7:37Introducing Machina
- 12:18Grafana integration example
- 21:38Results and lessons learned
- 25:55Q&A and closing
related talks
39mA Pythonic Approach to Continuous Delivery
41mEcosystem for Reliable Python Programming
01h 02mTools and Techniques for Infrastructure as Code
15mDevOps for Mere Mortals
31mFrom Dev Opps to DevOps
34mModern development environments for Pythonistas
51mTaking Python beyond scripting
27mI love being Pythonic