Salto interacts with your business applications via dedicated adapters. With your permission, an adapter can authenticate to your business application, fetch its configuration data to Salto, and deploy your changes from Salto to your business application. Salto’s adapters are available on this GitHub repo, and you can find their guides there.
A Salto configuration file is written in NaCl and determines what configuration elements Salto should manage for you. Whenever you add a new business application to Salto, its configuration file is set to its default values. You may need to adjust these values per your actual configuration, e.g., Salesforce CPQ customers may want to change their configuration file so that they can manage their CPQ work via Salto.
How to edit the configuration file?
The adapter configuration files can be found in your environments under the Files tab -> salto.config -> adapters directory.
In Environments, you can go to the environment Settings tab, select the relevant application connection, click the "..." menu and "Edit Configuration File":
What are the available configuration capabilities?
In general, Salto configuration files include the following sections and capabilities:
Fetch configuration:
Which metadata to include or exclude when fetching
How to generate Salto element IDs
Deploy configuration: various options which control how Salto deploys metadata
Client configuration: allowing to configure technical details like number of retries and timeouts of fetch when using the business application API
If you're looking for specific help for your business application, for example - how to exclude specific types in Jira or how to configure fallback users in Zendesk - search the help center documentation for dedicated guides on your issue. You'll be able to see configuration file examples there.
To learn more about each business application configuration capabilities, visit the appropriate page in the Github Salto OSS documentation:
Configuration Files and Deployments
As a best practice the include and exclude sections of the configuration files of the source and target environments participating in a deployment should be identical. Any changes applied to these sections in a configuration file of one of these environments, should be applied to the other environment before a comparison or deployment take place. You can compare the configuration files and identify differences by using any online text comparison tool, such as Diffchecker.