That's some terrible OPs and ridiculous single point of failure.

More proof that SlackOps/ChatOps is a failed methodology. I'm not quite sure what the fascination is with it. It's certainly neat for querying infrastructure but I certainly wouldn't rely on it for critical infra.

Maybe use this as an example that you guys shouldn't do that?

That feels like a leap too far. ChatOps should be a convenience, not the sole method of doing something. However conveniences are important.

I've had the luxury of building out an entire platform with ChatOps that built groups of people who had access to do deployments and mutate infrastructure.

It definitely was a neat project using chat flows, but I ultimately said "this is great until slack is down". Slack promptly went down the following week and we just threw our hands up and used the AWS console.

time to go home...

closes laptop. phew, short commute today.

the covid years sufficiently described

if i were a poet, i might have tried to put it in a meter. since i'm a coder, i made it a one-liner.

I'll do my next reboot at nine, I'll do my next commute with wine.