Skip to main content

Runops Releases #21

Runops REPL!#

No more typing the same boilerplate when running Tasks. Targets 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 Target. 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

CSV output#

You can now configure different output formats for Mysql and Postgres database Targets. 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 Target is of type "AWS" or "python". This is a great way to simplify Templates execution for Targets 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.

New integrations#

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 Targets. Set the redact option in the Target 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.

Other Enhancements#

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 Targets.

Custom markup