During deployments, users can make additional edits to NACL files. This can be done as part of any deployment, for example when deploying changes across two environments or deploying edits to a single environment.

By editing NACL files as part of a deployment, users can easily perform simple or advanced configuration changes, without the need to first do them in the business application itself. For example, a user may want to replace an email address used in some automation in staging when deploying it to production. Or, in more advanced scenarios, users can replace a value in many configuration elements, or introduce a large amount of new configuration elements created by some internal script.

Users can use Salto's built in editor, use an external web based editor, or use their own local IDE and tools for more advanced edits.

Elements are editable during these deployment steps:

This method works best for a small number of simple configuration edits - for example, changing single values, e.g. an automation's webhook URL when deploying to production.

To edit configuration elements' NACL contents, click the "Edit" button inside any element:

After editing one or more files, click "Apply Edits" to prepare a new Deployment Preview which includes your edits.

When using Github, Azure Devops or Gitlab, users can easily use a web-based code editor (based on Visual Studio Code) to perform NACL edits. This enables advanced edits, without requiring any local tools to be installed by users - for example, doing find & replace to change some string across your entire configuration.

To do this, first enable the environment's "Require Pull Requests" settings, as described in the "Integrating Pull Requests and Automating with Salto" article.

Then, inside the deployment, click the "Open in Web Editor" button, inside the Pull Request badge. This can be found during the "Deployment Preview" step of deployments, or the first edit step of single-environment editing:

After opening the web editor, do your NACL changes.

Once done, use the "Commit and Push" button to commit the changes to the relevant deployment "after" branch:

Salto will then automatically detect the incoming changes, and will ask the deployer to pull these commits into the deployment:

Users can clone their changes to some local environment, then use their own IDE, scripts and tools to make the required NACL edits. If using Visual Studio Code, you can also use the "Salto NACL Configuration Editor" VS Code Extension.

To do this, first enable the environment's "Require Pull Requests" settings, as described in the "Integrating Pull Requests and Automating with Salto" article.

Then, use the created pull request to make additional edits to the deployed elements:

Salto will then automatically detect the incoming changes, and will ask the deployer to pull these commits into the deployment:

When committing additional changes to Pull Requests, avoid force-pushing your commits as that may prevent Salto from pulling these changes properly.