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 application connections or deploying edits to a single applicaiton connection.

By editing NACL files as part of a deployment, users can easily perform simple or advanced configuration changes to their security applications, without the need to first do them in the security application itself. For example, 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 Tulip'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.

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

After editing one or more files, you can view your changes in the 'Unapplied edits' tab. Click 'Apply & Preview deployment' to create a new Deployment Preview that includes your changes, or 'Discard' to remove them.

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 connect your application connection to a git branch.
​

Then, inside the deployment, click the "Edit with Web Editor" button, inside the Edit Elements button. 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 branch:

Tulip 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 a 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 connect your application connection to a git branch.

Then, click the "Edit Externally" button in the "Edit Elements" menu.

A modal window with branch details and instructions will appear.

You can now use the created branch to make additional edits to the deployed elements:

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