We've just released the Dashboard page for admins on our Portal. 🎉
We moved a lot of furniture from place to place, and we found better locations for lots of stuff in our Portal. So get some water and get ready!
We are improving some visualizations and adding some really cool features to Runops. So ensure you have your seat belt and take that sip of water to stay hydrated while we go through the news!
We got some updates on the new task page for y'all!
- We did some design updates and added some features to the new task page. So buckle up because it's the first step to improving a lot more stuff in there:
- We added a fancy pants Combobox component to the application, so you can search for all your targets and make your workflow smoother while switching and selecting targets 🕺
- Proportion and use of space were adjusted in a way you can better visualize the logs of your tasks. We managed to decrease just a little of space from the editor but make a substantial increase of space in the logs, using the same total area 👀
- Selecting a target was placed on top of where the schema for your MySQL and Postgres database is loaded to improve the organization in the page 📄
- For every target you select, we change the URL so you can save that link and always have direct access to the targets you work with the most 🔗
- We still want to improve the use of space in the logs area, so some new design updates are coming on the tab component and in the actions of that page;
- We aim to make this page very close to an IDE (Integrated Development Environment), so many more exciting features and improvements are under development or discussion.
Stay tuned 📻
Here's a quick GIF showing this experience and two screenshots comparing how it was and how it is now:
GIF showing the Combobox experience:
How it was:
How it is:
The new year is here. We want to celebrate with you by sharing exciting new features that will make your life a whole lot easier.
Happy 2022 and let's dive in!
Use a large canvas to edit your scripts, logs loading automatically right bellow, and all your history of executions accessible as you run things.
When you are done with a Connection, easily switch targets to run different scripts.
Wanna re-run a script from yesterday?
Filter you history to find the script you need and re-execute a task with 2 clicks!
Hit cmd (mac) / win (windows) + enter to run your script from the canvas.
No need to copy and paste the same script everyday anymore.
If you have a script you need to run every day like database check or a financial report, you can now use the Runops step in Slack Workflows to schedule the execution of a task with a few clicks, all within Slack.
After the setup you get a message from the Runops bot with the results of your task every day at the configured time.
Check out this video on how to setup: https://runops.io/docs/portuguese-videos/#tarefas-agendadas
You can also use the Runops workflow step to create shortcuts.
Use Shortcuts to make scripts such as a report or a db check accessible trough a button available in the Slack chat panel.
The Runops bot speaks SQL!
If you like running tasks from Slack you will love this one. Now you can chat with the Runops bot using SQL! That is correct, you send SQL or any script in the chat and the bot replies with the results.
Here is how to use it:
- List the available Connections by typing
- Select a target by typing
- Start sending your script and get the results back for each message!
Check out this video for more details on how to use it: https://runops.io/docs/portuguese-videos/#chatbot
Improved Agent reliability
We released multiple enhancements to the Agent communication with the API.
The latest Agent version has increased capabilities in terms of how long a task can last, the size of scripts and outputs it can handle, and many other enhancements and bug fixes.
If you aren't using the latest version already, we highly recommend you upgrade your agents.
You can find the latest version along with the full details of the changes here: https://github.com/runopsio/agent/releases
You can now run NodeJS scripts in Runops. Many of you use Python or Ruby to create more complex automations, but now you can also use NodeJS.
You can see the list of npm packages available here: https://github.com/runopsio/agent/blob/main/Dockerfile#L116 - feel free to ask for new packages or contribute with suggestions.
New organizations can now signup for Runops from the browser.
Before this release new organizations were only able to signup from our CLI. Many people love the CLI experience, but this is not the case for everyone.
So go ahead and tell your friends from other companies that they should be using Runops and can start here: https://use.runops.io/signup
That is it for this update.
As always, please let us know of any feedback, suggestion, comment, or anything that comes to mind.
See you next time!
You can now use Runops in the browser! The web app experience is live for a few weeks and the feedback has been fantastic. Here are some of the things users love in the web app:
You can view your Tasks' history in a simple, yet powerful list. In the Tasks' detail view you can see review information, script, and logs!
Admins using the web app can manage users, targets and agents!
- Create, deactivate, and update users' groups.
- Create and update Connections.
- See your organizations' connected agents and metadata.
Now, instead of controlling access to Connections using roles, and reviews with teams, you use only one property: groups. Plus, we added the capability of controlling access to templates using groups.
We made some structural changes in the last few weeks to Runops. Despite the size of the changes, most of you didn't even notice it. This is because we invested a lot of time in improving our reliability. We are not only fixing problems faster when they happen, but even fixing them before you notice. Some of these improvements include:
Runops Agent runtime instrumentation. The Runops Agent now loads and exports runtime configurations. This improves our visibility into problems and increases our abilities to fix problems in the agent without involving your team.
Central monitoring tool. All our systems now use the same central error monitoring and tracking system. This system makes sure that we get notifications for any problem that happens in any system. Notifications include all the metadata on the problem, including the individual user and organization. This is why you get messages from our team when you have problems even before you think about reaching out.
We simplified the Runops authorization mechanism!
Now, instead of controlling access to Connections using roles, and reviews with teams, you use only one property: groups.
Plus, we added the capability of controlling access to templates using groups.
What are groups?
Groups are a simple concept to grasp and will enable us to add even more powerful features in the future. In a nutshell, you add users to one or more groups. Groups can map to your teams, squads, locations, anything you want. With these groups, you then manage access to Connection, Reviews, Templates, and more. It's a very light and easy to use RBAC mechanism.
What do you have to do?
Nothing. We migrated all your teams and roles to the groups property.
You don't have to do anything.
Just use groups the same way you used teams and roles from now on.
What about Roles and Teams?
team and 'roles` of the user are still there. They are now only metadata about the user to help identify the user in the Slack review card. These fields won't be use for decisions anymore.
When does this ship?
We are rolling out this feature over the next couple days. We have been using it for a few weeks and it's amazing! Your organization should get it soon.
Where can I learn more?
Check out the docs to learn more.
See you later!
No more typing the same boilerplate when running Tasks. Connections without reviews return the logs of a Task right the way. We added a new command to the CLI: runops tasks repl -, where you can start an interactive session with your Connection. In the REPL session, you only type the script option and get the results. It's simple. The REPL also supports multiline scripts. Here is a preview of how it works:
You can read more here: https://runops.io/docs/user-guides/REPL
You can now configure different output formats for Mysql and Postgres database Connections. These types show tabular results by default, great for quick consumption in Slack or the CLI. However, for more advanced analysis, it's best to be able to open the results in a spreadsheet. So you can use the configuration FIELD_SEPARATOR to set different separators for the output. For instance: setting the separator to: "," - will generate a beautiful CSV ready to be open in Excel or other spreadsheet apps.
Custom type for Templates
You can set the type of the Task for a Template using the file name. Runops will try to match the extension of the file to a valid type. For example, the file "my-query.MySQL" as a Template creates a Task of type MySQL even if the Connection is of type "AWS" or "python". This is a great way to simplify Templates execution for Connections that support multiple integration types. Also, with the type attached to the Template, you don't have to set it when running a Template from Slack or the CLI.
Hashicorp Vault You can now use Runops to interact with Hashicorp Vault. This is great for automating one-off tasks such as creating database users for new applications. Using a Template, you enable everyone to run sensitive operations in Vault that only executes after review. So, instead of doing everything yourself, you become a reviewer, taking way less of your time while still keeping security and compliance in place.
Kubernetes + Rails Use the k8s-rails type to enable access to the Rails console of applications running on Kubernetes. Then, using the Runops REPL, you authenticate with Google and get an experience similar to the Rails console. Zero hassle and risks of distributing SSH keys, Kubernetes credentials, VPNs, and other things required to get a shell running side-by-side with your production application.
Version checker in the CLI
You will get a message when a new version of the CLI is available. This is because the CLI checks the latest version in the most used commands. The check happens in parallel, so there is no impact on the execution latency of your commands. The message stops showing up after you update the CLI.
PII data redact configuration
You can now disable the automatic redacting of PII data for specific Connections. Set the redact option in the Connection to "none" to remove redacting, or "all" to remove all sensitive data. The "all" option is the default. For now, only all and none are available. You will be able to fine-tune redact specific data types in the future.
We removed the tutorial from "runops login" command. It only shows up in the runops signup option now. You can use the PUT users API endpoint using the email to identify the user. This is useful for integrations to activate/deactivate users from your internal systems without the Runops user id. The new Runops agent is now the default for the hosted and self-hosted options when creating new Connections.
We are excited to announce many of the top requested features that we released over the last few weeks. Let's dive in!
Runops API is out
You can start using the Runops API to build automations and integrate them with your existing tools. The list of endpoints and their specification is available in the docs (https://runops.io/docs/api). One use case requested by many of you was the user management API to integrate existing employee credentials provisioning systems, and we released it!
You can now add, update, and remove users using the Runops CLI. The create users option is an additional way to bring new members to Runops, in addition to the self-register option from Slack and CLI. You can also update user's status to activate/deactivate accounts and change users' teams and roles.
Role-based access control
Control who can access what Connections. You can now group Connections into roles and attach these roles to users. A user only sees the Connections allowed by their roles.
Kubernetes Secrets support
You can now store secrets and configurations in your Kubernetes Cluster secrets. In addition to Hashicorp Vault and AWS Secrets Manager, this new secrets storage mechanism makes it easier to get started before you move to a proper Secrets Manager.
🎨 Improved outputs in the CLI
You won't see JSON outputs as the result of commands anymore. The CLI now displays all outputs as tables. When creating Connections or running Tasks with reviews, the CLI displays all the information you need in an easy-to-read table.
✔️Improved validations for Tasks execution
You will get a detailed error message when a specific secret or configuration is missing for a given Connection type. The agent now performs an extensive set of validations before running a Task. Works both when creating a Connection or running Tasks.
🔌 New integrations
You can use a range of new integrations in Runops. Use bash for running arbitrary shell commands. With k8s-apply you provide a YAML, and Runops applies it to Kubernetes clusters (we are using this one internally). Use rails to access a Rails application and rails-console get a Rails console experience, but with all the controls of Runops. You can check the complete list of integration in the docs: https://runops.io/docs/concepts/integrations
📑 Revamped docs
You will have a better navigation experience in the documentation. Find dedicated sections to end-users and operators in the menu. The docs also got additional guides detailing the Kubernetes Secrets support. Check it out: https://runops.io/docs/quickstarts/kubernetes
🐛 Bug fixes
Fixed bug in redact logic that broke emails format.
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.