Skip to main content

Runops Releases #19

ยท 2 min read

We have been working hard the past couple of weeks to get this release out, and it's finally here! The new Runops agent is available, and it brings huge improvements to the Runops experience. We also launched a new version of the web app to get metrics and graphs on the Tasks executed and manage users' status. Let's dive in!

๐ŸŽ 10x improvement to execution time: from 50 to 5 secondsโ€‹

The new Runops agent brings the execution time from 50 to 5 seconds. The experience in the CLI got closer to the interactive experience of directly accessing a database or container. Slack users won't even notice a delay anymore.

๐Ÿ›ฐ Simplified deployment modelโ€‹

One instance of the new agent can execute Tasks from N Connections. This means that there is no need to set up a new agent for every new Connection you add to Runops. Using a tagging system, you can configure which Connections run on which agents. A typical pattern is setting up one agent per environment and then using these same agents every time you need to add a new Connection to Runops.

๐Ÿ” Secret Managers integrationsโ€‹

You can now keep your secrets in the Secrets Management solution of your choice. There is no need to add Secrets to Runops anymore. Your secrets stay in your vault, and the new Runops agent will pull a temporary credential to execute Tasks. We already support Hashicorp Vault and AWS Secrets Managers, with GCP Secrets Manager and other providers coming soon.

๐Ÿ“ˆ Metrics, Graphs, and Users Management in the web appโ€‹

The revamped admin app has metrics and graphs that enable you to understand how your company uses Runops to access infrastructure. You get average review times and which teams are more active, besides the complete picture of Tasks and their details. Now you can also activate or deactivate users in the Users Management section.

๐Ÿž Error logs in Slackโ€‹

We fixed a bug that prevented you from seeing the result logs of Tasks that failed in Slack. The logs were sent as binary, and you had to download them and open them on your computer to see why the Task failed. Now we send results as text. You will see what happened in case of success or failure directly in Slack.