Skip to main content

Tulip App Configuration

Customize which parts of your configuration to manage with Tulip

Support avatar
Written by Support
Updated over 4 months ago

Tulip interacts with your enterprise security applications via dedicated adapters. With your permission, an adapter can authenticate to your application, fetch its configuration data to Tulip, and deploy your changes from Tulip to your application.

A Tulip configuration file, written in NaCl, determines what configuration elements Tulip should manage for you. Whenever you add a new security application to Tulip, its configuration file is set to its default values. You may need to adjust these values per your actual configuration, e.g., Okta customers may want to change their configuration file so that they can manage their Okta users via Tulip.

How to edit the configuration file?

The adapter configuration files can be found in your app connection settings under the General tab.

What are the available configuration capabilities?

In general, Tulip configuration files include the following sections and capabilities:

  1. Fetch configuration:

    1. Which metadata to include or exclude when fetching

    2. How to generate Tulip element IDs

  2. Deploy configuration: various options which control how Tulip deploys metadata

  3. Client configuration: allowing you to configure technical details like number of retries and timeouts of fetch when using the application API

If you're looking for specific help for your security application, 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 application configuration capability, visit the appropriate page in the Tulip documentation:

Configuration Files and Deployments

As a best practice the include and exclude sections of the configuration files of the source and target application connections participating in a deployment should be identical. Any changes applied to these sections in a configuration file of one of these application connections, should be applied to the other application connection 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.

Did this answer your question?