Connecting a Salto environment with a Git offers the following advantages:
Documentation: Keep a record of all configuration changes to ensure they’re easy to trace. This will simplify the process of identifying previous changes during audits.
Integrate with Ticketing Systems: Connect changes directly to business requirement tickets for improved tracking and accountability.
Collaboration: Improve teamwork and code quality through pull requests (PRs) and peer reviews.
Automation: Leverage continuous integration (CI) jobs to automate testing and validation of changes before they are deployed
When connecting to git, you can choose which one of these features you’d like to use. We recommend users to start with the basics of documentation and integration with their ticketing systems, then proceed to more advanced features such as collaboration and automation.
📌 Salto follows a 'Branch per Environment' approach, where each environment is linked to its own Git branch. Each branch keeps a textual record of the environment’s latest configuration.
Documentation and Integration with Ticketing Systems
When connected to Git, Salto keeps the environment branch synchronized by automatically pushing any configuration changes, whether deployed through Salto or identified during a fetch operation. This creates an in-app change log of your application’s configuration, backed by Git, allowing you to attach a ticket to these change log entries. Get started
Collaboration using Pull Requests
Salto enhances teamwork and code quality by making deployments dependent on pull requests (PRs) and peer reviews. When enabled, a Pull Request will be automatically created for each deployment made in Salto. If a PR is attached, deployments will only be allowed if their PRs are mergable in git. This allows you to configure branch protection rules in Git, ensuring peer reviews and approvals are required before any changes are deployed to the environment. Get started
CI/CD and Automation
Attaching pull requests to Salto deployments enables integration with continuous integration (CI) jobs to automate testing, validate changes before deployment, and run external tools like static code analysis.
You can enhance your branch protection rules to require these jobs to complete successfully before allowing changes to be deployed to the environment. Get started