by slajax on 7/27/20, 5:04 PM with 35 comments
by slajax on 7/27/20, 6:27 PM
The key idea is that you build a CLI using our SDK (it's a container) and then we make it instantly accessible to your whole team in Slack, while also providing 12 factor principals such as Secrets, Configs, Logs, Events and Metrics.
We are early on but have a very vibrant and growing Slack community of developers who want to build their own Cloud PaaS using AWS, GCP, Azure etc but want an easy to use DX so they can distribute there knowledge and process to others and save themselves tons of time and context switching.
Please AMA, we'd love to hear your thoughts.
by mistedissetanti on 7/27/20, 9:09 PM
Now, aside from the implicit risk that this might offer, if Slack acts as the "Control plane" for DevOps, what's the platform's "Data plane"?
Is it right to assume that in order to be independent from Slack we'd need to rely on CTO.ai's own infrastructure and resources? I.e. the data plane where DevOps "effectively happens"
by jasonpeacock on 7/27/20, 7:09 PM
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.
by schoolornot on 7/27/20, 9:42 PM
by eslamsalem on 7/27/20, 6:24 PM
by jacksonpollock on 7/27/20, 7:28 PM
by deeblering4 on 7/27/20, 6:25 PM
by dvohro on 7/27/20, 5:13 PM
by kaseyluckk on 7/28/20, 3:37 AM
by jmlimit on 7/27/20, 7:41 PM
by gman2121 on 7/27/20, 8:42 PM