Videos / DevOps

Episode 12 of 14 · DevOps, end to end

Infrastructure as code: the state file is the whole story

Chapters

1. The console at two in the morning0:00
2. No history, no blame line0:16
3. No review, no second pair of eyes0:32
4. You cannot build it twice0:48
5. The person who remembers1:03
6. The file becomes truth1:21
7. A destination, not directions1:39
8. A resource, and its address1:57
9. References become edges2:15
10. The graph decides the order2:31
11. Read the plan before it runs2:48
12. The plus, the tilde, the minus3:05
13. The ledger with the receipts3:23
14. Without it, everything is new3:40
15. Not on a laptop3:57
16. Remote, versioned, encrypted4:15
17. One apply at a time4:34
18. What drift actually means4:52
19. Copied three times is a function5:08
20. Inputs, outputs, and nothing else5:26
21. A root that only wires5:44
22. Pin the version6:01
23. The environments as branches trap6:17
24. Same shape, different numbers6:36
25. The estate that already exists6:54
26. Import binds an address to an id7:12
27. The empty plan is the test7:30
28. Import in slices7:47
29. Renaming is deleting8:04
30. The two deploy dance8:21
31. The pull request is the airlock8:40
32. Apply from exactly one place8:58
33. Apply the plan you reviewed9:15
34. Never edit state by hand9:32
35. Small states, small blast radius9:51
36. What it still does not fix10:09
37. The whole thing10:28

Infrastructure as code: the state file is the whole story. Somebody opened the cloud console at two in the morning, ticked one box, and the outage stopped. Eight months later nobody can say which box, or why, and staging does not have it t

Mark as watchedSaved in this browser only.