3 ms·

All of the things mentioned in the article seem more a result of bad IaC, instead of general IaC... > Packages go out of date. Features are deprecated and stop

All of the things mentioned in the article seem more a result of bad IaC, instead of general IaC... > Packages go out of date. Features are deprecated and stop working. Code syntax changes. Images are no longer available. This is true for all code and we have tried and tested methods/principles for dealing with that. > Someone’s user account got built in, and they don’t work here any more. No comment needed. > He was in the Prod directory — and starting nuking production. Say it with me: Elevate Permissions

scaryclam 3y ago
> Say it with me: Elevate Permissions I always tell my team that we should be able to build and deploy from our laptops. That we should make sure we don't bake our build/deployment into third party systems, so we're still able to do things when they have outages and can move to a different one if they become unreasonably priced etc. But that we SHOULDN'T be doing those builds/deploys from our laptops UNLESS it's an emergency. Almost no dev needs a key for the whole production infrastructure sitting on their laptop, they don't need a production DB superuser. They should know how to get access to things when needed, but embrace the safety of not being able to accidently kill something important. I love having the power to destroy a whole companies offering at my fingertips, but the terror of running a command and realising you're doing it by accident is just not worth it.