Big week: non-technical workflow in Slack, CLI 0.2.0, better Task statuses, and more. I'm excited, this was one of our biggest weeks for releases.
With today's releases, we enable non-technical workflows. Non-engineers can start leveraging Runops! Making a SQL query or a python script available for Customer Success or Product Managers to run from Slack now takes 10 seconds: just add the script to Git!
/runops templates anywhere in Slack to get started. You can select the template from a dropdown and we will create a dynamic modal with one input field for each parameter in your Template.
You can start Tasks executions from Slack. When a Task is fully approved we send you a button to trigger the Task run. After the Task finishes executing, you will get the logs in a file from the Runops bot.
With the release of the version 0.2.0 of the CLI, the type and message flags are optional when creating Tasks. Now you only need to provide the Target and the script. Quickly run scripts on Targets without reviews, we get out of the way:
runops tasks create -t test-db -s 'select 1'
To make the experience more consistent, we moved the -t flag from the type to the target, as type isn't going to be used much now. You can still use it to override the type from the Target using the -y option.
Now you get a notification in Slack about the status of your Tasks. Both failure and success outcomes are updated in the Task so you can check them in the CLI, admin UI, or Slack. ▶️ Autorun Tasks Tasks that require no review will automatically run when created. You can get the results back from a script with 2 commands now instead of 3.
🐞 Fixed bug for list Targets and Tasks on older Mac versions 👾 Improved install script with npm config checks and input for key 📚 Simplified Getting Started guide
Check out all previous releases [here]([[⚙️ Runops Releases]]). As always, let us know what you think! Any thoughts, comments, critiques, are very welcome.