What you've basically created is automated change control, but lacking some change control features. You might want to add a set of features specific to managing change control, because otherwise I'll have to build a change management system around this. > You run an AWS CLI command in the terminal and it goes to Runops instead of AWS Most enterprises are wary of handing over control to a vendor, especially if it's t…
I agree with many of these points, here are some thoughts on how we deal them: > Most enterprises are wary of handing over control to a vendor Great point, we do have the Enterprise version, which is self-hosted. > Do you find a lot of Lisp/Clojure devs out there for when you need to expand? We won't hire engineers based on the language they know, but instead in general engineering skills, and they can learn Clojure…
Here's some of the things a typical IT CM process handles: How do you properly surface and acknowledge the risk & impact of a change? What are the order of operations & how do you track them? How do you validate an operation? Roll back? Are there governance structures in place (X team can run Y task in Z environment)? With multiple stakeholders, how do you get approval from everyone, or handle change overrides? How do you run 'almost' the same thing in different environments? Do you use multiple communication/coordination methods, like e-mail, MS Teams, Slack w/multiple workspaces/orgs, Zoom, Jira, ServiceNow, etc? Is there a "change plan" which is drafted, edited, published, approved, and executed, in coordination with multiple teams?
All that may be overkill for your tool, but it's some of the stuff I would need to build around it to use it in my enterprise. Otherwise I (the ops guy) would need to build & run all those steps and coordinate with others when it's time for them to perform their steps (release, validation, debugging, rollback, etc).