Skip to main content

Tied Hands Engineers

The worst thing that can happen to an engineer is to get paged out-of-hours only to realize they can't fix the problem on their own. They did all the hard work of waking up, debugging the problem, and finding a solution. But when it's time to apply the fix, they don't have access. Time to call a DevOps engineer to get permission or have them run the patch.

DevOps means developers run their own code, but how can a developer operate a piece of software if she can't access the database, the cloud provider, or the Kubernetes cluster? Only a handful of people has access to these resources at most companies today.

This problem is not just bad on out-of-hour pages. DevOps teams centralizing raw access to production are bottlenecks to the whole engineering team. A simple query in the database to troubleshoot a problem can take hours for the busy and sad DevOps team to process the request in their queue.

It's not ok to keep making direct updates to the database or change things in the AWS console all the time. CI/CD and infrastructure as code are great tools. But direct access will happen no matter how much automation a company has. Restricting raw access to a few engineers results in bad culture incentives and an environment with low trust and autonomy.

Runops democratize access to production to enable DevOps. We fix this problem by adding security and compliance into easy-to-use clients. Runops enable any engineer to make production access with security and reliability.

Runops is a client to databases, AWS, Kubernetes, and others. Users access Runops from Slack and a CLI. We make accessing cloud resources easier than installing multiple clients and using VPNs. Runops also improves security and GDPR compliance.

Runops Releases #18

馃摎 Revamped documentation website#

We completely revamped the Runops documentation website. It's now easier to navigate and has a better design. We also enabled the chat support widget to the docs. Now you can reach out anywhere in the docs to talk to us. The new website is also hosting our blog, where the Releases and other articles are shared.

馃檹 Thanks#

That is it for this week, we'll see you next week with more Releases.

As always, please let us know of any feedback or comments you might have on Runops.

Thanks!

Runops Releases #17

馃幆 Select Task type in Slack#

You can now override the type of a Task in Slack. We added a new menu option that you can use to change the type from what is set in the Target when creating a Task in Slack. It's an optional field, so if you don't provide it, the type set in the Target is used.

馃檹 Thanks#

That is it for this week, we'll see you next week with more Releases.

As always, please let us know of any feedback or comments you might have on Runops.

Thanks!

Runops Releases #16

Andrios

Andrios

Engineering

Improved logs experience in Slack, Targets pagination in Slack, improved analytics and security#

馃搥 Logs in Slack#

We improved the delivery of logs in Slack. The Task logs are now delivered as an attached file to Slack for logs with less than 5MB in size. You can see the results directly in the message instead of having to download a file to your computer and open it. The download link continues to work for logs with more than 5MB in size.

馃幆 Targets pagination in Slack#

We added a button to the Slack Tasks execution UI that let you paginate Targets. This is useful for organizations with more than 100 Targets. By default the UI will load the first 100 Targets and you can use this button to load the next 100 Targets in the org.

馃И Improved analytics and security#

This task has no direct impact to how you use Runops today. We worked on improving the measurements of the app to further improve your experience and had an external party perform a penetration test to the Runops API. The results were great, let us know if you want to get access to the report.

馃檹 Thanks#

That is it for this week, we'll see you next week with more Releases.

As always, please let us know of any feedback or comments you might have on Runops.

Thanks!

Runops Releases #15

Andrios

Andrios

Engineering

馃獩 Enhanced Templates execution#

We fixed a bug that prevented Templates from running when the number of Templates in the Github repository increased. Templates now run faster and there is no limit to the number of Templates in the repository. We also updated the CLI experience: the Templates list now return just the names and to get the parameters of the Template we created a new command: runops templates get --name {template-name}. This makes it easier to read the output in the terminal and also helps for a faster Templates experience.

馃檹 Thanks#

That is it for this week, we'll see you next week with more Releases.

As always, please let us know of any feedback or comments you might have on Runops.

Thanks!

Runops Releases #14

Andrios

Andrios

Engineering

ECS exec Tasks, CLI Sign Up, Compliance enforcement, and major CLI experience improvements.#

馃搰 ECS Exec commands integration#

You can now use Runops to access running containers in AWS ECS, using the ECS exec feature recently launched by AWS. This means that you can get a shell inside ECS containers without bastion hosts or exposing your private network to the internet. The access happens trough the AWS internal infrastructure. You get the all the auditing capabilities of Runops along with the AWS Cloud Watch trails for every command. It's a great alternative to manage and control access to the Rails and Elixir consoles in production.

馃拡 Sign up from the CLI#

We are really excited about this feature! Anyone can Sign Up for Runops directly from our CLI. New organizations get created when the first user in the company signs up with a company email. Users joining existing organizations can also use the CLI to do so. The runops signup command in the CLI will route an user to the right workflow. We will identify the organization from the company's email domain. The approval mechanism in Slack for users joining an existing organization stays the same.

馃崶 Major CLI experience improvements#

The admin experience is way better in the CLI. The CLI now requires the minimum amount of parameter for any operation. You can do things like add new secrets, update runner, change the type, all providing only what you meant to change. Before this update you had to provide parameters you were not changing like the type and review mode for every command. We also cleaned up null values present in json-formated responses.

Compliance-enforced reviews#

The teams review mode got a new compliance enforcement feature: the creator of a Task can't review their own Tasks. This is important for companies that have resources with shared responsability across teams and require this type of locking mechanism.

馃檹 Thanks#

That is it for this week, we'll see you next week with more Releases.

As always, please let us know of any feedback or comments you might have on Runops.

Thanks!

Runops Releases #13

Andrios

Andrios

Engineering

This week we focused on a big improvement to the logs!

馃Ы Gigantic logs improvement#

We removed all the clutter present in the logs of every Task. Now the logs from your tasks will get just what came back from your command. No additional clutter making it hard to find the cause of a problem or the results you were actually looking for in the logs. Enjoy!

馃檹 Thanks#

That is it for this week, we'll see you next week with more Releases.

As always, please let us know of any feedback or comments you might have on Runops.

Thanks!

Runops Releases #12

Andrios

Andrios

Engineering

Big improvements to logs, Azure and Terraform integrations, create tasks from Slack, and more!#

Another week packed with big enhancements to Runops! Let's dive in 馃た

馃 Unlimited task log size#

We removed the 5MB limit to the size of Task result logs. For large results that don't fit in a Slack message or Terminal stream, we will send a temporary URL where you can download the logs from. Now you can run tasks with no limits to the result logs size.

馃獰 Azure and Terraform integrations#

We released integrations for the Azure CLI and Terraform. Now you can automate Terraform deployments and access the Azure CLI from Runops.

馃挰 Create Tasks from Slack#

The Runops bot in Slack got a new command: /runops tasks. It enables you to create Tasks from Slack. You can create SQL or any type of Task, get reviews, and run them from Slack. If you don't love the CLI interface, you don't have to use it anymore :)

馃М CSV output for Mysql and Postgres#

Now you can set a Target to return CSV formatted outputs for Postgres and Mysql. You can set the type of the Target to mysql-csv or postgres-csv and that is it. And remember: you can always override whatever type is set in the Target when creating a Task: pass in the type (-y) flag when creating the Task from the CLI.

馃檹 Thanks#

That is it for this week, we'll see you next week with more Releases.

As always, please let us know of any feedback or comments you might have on Runops.

Thanks!

Runops Releases #11

Andrios

Andrios

Engineering

CLI OAuth 2.0 authentication and data security improvements#

馃攼 CLI OAuth 2.0 authentication#

Now you can authenticate in the Runops CLI using Google, Github, or a custom username + password of your choice. This is an improvement over the previous key-based authentication. Now we only store Bearer tokens locally. Tokens expire and get renewed often. You can now use additional authentication factors trough Google and Github integratinos.

鈵 Data security improvements#

We removed all potentially sensitive data access by Runops. The logs from your tasks now get PII redacted before they touch any storage mechanism. Now besides not storing or having access to your secrets, we apply the same principles to your data.

Runops Releases #10

Andrios

Andrios

Engineering

Create new users from Slack and synchronous Tasks execution.#

This week brings two important updates that will make Runops a lot better.

馃挰 Create new users from Slack#

Now everyone in your Slack workspace can join Runops, automatically! Anyone can type the /runops register command anywhere. We will ask for a few extra information and notify an admin. After the admin approval, the user is ready to use Runops! All happening within Slack.

鈵 Synchronous commands#

When you create a Task with the CLI or Slack, they will run and return the logs automatically for Tasks without reviews. This is great for user Runops as a replacement to the CLIs you use today to access things in real-time. Type a command and get the results, just like you do using the tools directly, but with all the goodies of Runops.

Custom markup