That sounds about as natural as using Xbox Kinect gestures. Additionally, your SLA is now also tied to Slack's, which is a multiplicative downgrade.

Not every integration makes sense. I know some companies doing business logic automation in Google Docs, and I'm also reminded of Twitch Plays Pokemon. Just because you make a choice to integrate with a product doesn't mean it's widely adopted, practical, or wise.

Or supported.

Edit: I want to clarify. I don't mean to be rude, and I wasn't in the room when y'all made these decisions. I just don't think Slack is the ship you want to tie yourselves to, especially not as your control plane.

> I know some companies doing business logic automation in Google Docs

Sorry, but I have to post this now:

https://github.com/learnk8s/xlskubectl

"xlskubectl integrates Google Spreadsheet with Kubernetes."

"You can finally administer your cluster from the same spreadsheet that you use to track your expenses."

It's a (working) joke of course, but a hilarious one.

If they are like me, they use chatOps as a way to consolidate and shortcut different commands and dashboards. But by no means are operations dependent on our chat. If chat goes down, then you will simply need to login to our ci/cd service to initiate deployments, rollbacks, etc.

That sounds painful for an ops person. When I did ops work I much preferred to have as little abstraction as possible seeing how critical each action is.

I would never want my production deployment rollback tied to my instant messenger plugin working.

How often are you rolling back production deployments that you need a Slack command to do it? Perhaps I am missing something but this does not seem like a good use of time for whoever put it together.