We use "Infrastructure as Code thing[s]" but no way would we use, say terraform, to execute a change to a public-facing DNS record without confirming whether it was an update or a destroy/create operation. I'm not shaming someone who does, or did, and I love Rachael by the Bay, but there seemed to be a wee bit of snark coming through with respect to all the "magic" layers of stuff that makes things work in the cloud. I don't know if it's the old "the cloud is just someone else's computer" thing that you often hear, but honestly I wish we'd get over it. Cloud computing has been transformative, and there are lots of business that are able to exist because of the efficiencies derived from these platforms. I don't think there's much question that cloud deployments can be done correctly and managed well, and after all there is always someone upstream whose competence you rely on.
Something I've learned over the past 3 years or so is that when you have Infrastructure as Code, you get Infrastructure by Coders. This is incredibly empowering and useful, but sometimes little details sneak into the system because the folks writing the code don't have any experience managing the systems that have been so neatly abstracted. Or, as could be the case here, they choose to simplify the interface by making a number of policy decisions by default...such as make before break when revising DNS A records.
