Managing configurations across environments often involves handling values that inherently differ, such as webhook URLs, domains, or email addresses. When comparing two environments - these values differ, and this difference should be maintained rather than “corrected”. To address this, we’re happy to introduce Environment Variables, a new feature in Salto that automates and simplifies the process of managing environment-specific values.

What are Environment Variables?

Environment Variables let you define and manage fields that require unique values across environments. For example, a staging environment may use a webhook endpoint URL like https://staging.acme.org, while production requires https://prod.acme.org. By using Environment Variables, you can:

• Ensure the correct values are used in each environment.
• Automatically replace values when deploying configurations between environments, so that the correct one is maintained in each.
• Focus on meaningful differences by hiding irrelevant mismatches caused by environment-specific values.

How Environment Variables work

1. Define scope

Environment Variables start with defining the scope of fields to replace. Scopes are defined using Salto Selectors, which allow for precise targeting of configuration fields. Examples include:

• Replace all Zendesk endpoints: zendesk.webhook.instance.*.endpoint or (same applies for Jira, Okta, etc.)
• Replace the endpoint in a specific Zendesk webhook (Jira webhook, Okta inline hook, etc.)

2. Set environment-specific values

Each Environment Variable includes values for specific environments. During deployment, Salto will:

• Replace the value if the source environment value matches the variable’s definition.
• Use the target environment’s defined value, ensuring consistency.

For example, if https://staging.acme.org exist in staging and https://prod.acme.org is defined for production, Salto automatically ensures the right values are deployed to the appropriate environments.

3. Comparison and deployment

• When comparing environments, differences covered by Environment Variables have will be shown with a designated annotation, allowing you to focus on meaningful changes.

• Deployment previews highlight replaced values and the Environment Variables that triggered the replacement, ensuring clarity.

4. Creating Environment Variables

Once you configure an Environment Variable - Salto will use it for all future deployments. You can create Environment Variables in two ways:

• From Comparison Views: During deployment, you can identify differences and create variables directly from the comparison screen. Customize scope and values on the fly.
• From the Environment Variables screen: Access this via Org Settings, where you can manage, edit, and delete variables.

5. Alerts and Transparency

• Salto alerts you when differences involve values defined only on one side (e.g., a value for staging exists, but not for production).
• Deployment previews clearly mark replaced values and the Environment Variable responsible, ensuring visibility.

If you need help with your setup - please reach out and schedule a 1:1 session, or start on your own with our free trial.