Hacker News new | ask | show | jobs
by jasonpeacock 2146 days ago
What happens when Slack is down? Does DevOps also stop, or is there a way to do the same commands/workflows outside of Slack?

You don't want two separate run books, as they'll never stay in sync. It'll already be enough of an efficiency hit just switching to an alternative interface when Slack is down, let along switching to different tools/processes.
2 comments
ruxandrafediuc 2146 days ago
Hey Jason, Ruxandra here from the CTO.ai team!

You have the freedom to build your DevOps workflows as you please, by leveraging our SDKs to interact with the tools and platform you use daily for DevOps. The Slack interface allows you to customize the inputs and trigger these workflows as you desire, but--once triggered--you will not necessarily depend on Slack being up. Hope that makes sense!

Also, the workflows you automate using our platform work in the CLI as well. So you build once, you get a containerized automation which you can use either locally in your CLI, or in Slack. For running these locally, you have to install our `ops` CLI on your machine (more on this here: https://cto.ai/docs/start-building-ops).

Let me know if that helps clarify your questions or if you have any other questions. Thanks!

link
slajax 2146 days ago
Founder here - great question.

The way this works is that you first build a CLI, which is a container and then you publish it to us so that it also runs in Slack. It's shared code that runs in both environments.

So if Slack is ever down, you still have the CLI.

The big benefit here is that you build once and it runs in both places which means don't need a separate runbook or even infra to make your CLI run in Slack - it's 100% serverless.

For our users the Ops engineers obviously prefer the CLI, but the Dev's really love Slack - this creates a nice balance in the DX that works on both sides, on top of existing CI/CD.

link