Re-running your code brings back everything except the data

Luca Berton created Ansible Pilot and spent three years on Red Hat's Ansible team. Earlier, he held a VP of Infrastructure role at JPMorgan Chase. His work has since moved toward AI agents that read alerts and act directly on production systems,

In this session is we’ll walk through some of the patterns he sees teams walk into now: 

• An AI agent gets a loose cleanup instruction and runs a destroy that takes years of records with it. 
• A Terraform rename that changes no values deletes a database nobody meant to touch. 

Infrastructure-as-code recreates your infrastructure, not the data inside it. Re-running a playbook rebuilds the host and leaves the corrupted rows exactly as they are. A snapshot can take you back, but it rolls the whole resource to a past moment, and every good write since goes with it. Nothing in that toolchain recovers only the damage.

Live attendees only: Luca and host Ohad Maislish take a real incident from the cases above and build the recovery that team wished they'd had, one step at a time. Ohad has built IaC tooling himself, so his pressure testing will dig into why the code behaved as it did. Bring an incident of your own, a change that broke production and passed every check, and they'll test the finished runbook against it live.

Ask Luca and Ohad questions in the chat throughout the live session.

Join us to hear:

• The bad writes that pass every gate: migrations gone wrong and over-scoped agents whose corruption never trips an alert
• Why reproducible infrastructure doesn't mean recoverable data: what a whole-resource rollback costs in good writes, and how to scope recovery to what actually changed
• Where Luca lands on the community's argument that disciplined IaC plus snapshots already adds up to a disaster recovery plan

Register even if you can't make it, and the recording will land in your inbox by the next morning.