The automated change log that ensures no changes will make it to production without you knowing

We all want to have a beautiful, harmonised DevOps process— a perfect flow where every change is meticulously tested in a staging environment and approved via pull requests before reaching production. 

But, reality, right? 

People still make changes directly in production, and it happens frequently for various reasons. Sometimes, it's a critical hotfix, a seemingly insignificant tweak, or simply an element that's more convenient to modify in production (Salesforce layouts, anyone?).

As a result, direct production changes occur, environments drift, and it becomes unclear what's actually implemented in production.

In a survey conducted earlier this summer, 65% of respondents indicated that tracking changes in their environment is one of their biggest challenges.

That’s why we’re excited to introduce our new automated Catch-it-all change log. This automated change log provides complete visibility into all changes made to an environment, whether through a Salto deployment or directly. This ensures that everyone on the team is aware of all changes, enabling better planning and avoiding conflicts or overwriting each other's work.

How It Works

The new Change Log tab captures all changes made to a single environment and organizes them based on when they were introduced and how;

• Deployments - Changes deployed to the environment using a Salto deployment.
• Fetches - Changes made directly to the environment, captured by Salto through an automated environment fetch. The frequency of these automated fetches is flexible - users can choose to run them hourly, daily, or weekly.
  
  

By using the Catch-it-all change log, your team can maintain a clear and accurate record of all changes, promoting better collaboration and more efficient DevOps processes.

‍

Built-in documentation - In addition to tracking the history of all the changes in the environment, you can also leverage  Salto to document them. The change titles are editable, either through the deployment or through the change tab, so teams can edit the change title and include details about the changes as well as its respective Jira ticket.  

Version control integration - Teams using Git can automatically sync their change log with a Git branch, ensuring a maintained source of truth branch. 

Restore options - By maintaining a log of all changes made to an environment, Salto can restore the environment to a previous version with just a few clicks, enabling quick recovery from any production issues. 

‍

Salto’s new Catch-it-all change log revolutionizes how teams track and manage changes in their environments by offering full visibility into both in-process and direct production changes. With built-in documentation, Git integration for version control, and easy restore options, teams can now maintain a clear and accurate record of all changes, enhance collaboration, and quickly recover from production issues. 

‍