Configuration Management Across Environments

Promoting a resource moves the resource itself (a module, style, or service definition) but not the environment-level configuration that surrounds it. Each Unqork environment maintains its own independent configuration: API credentials, SSO settings, session policies, and integrations. A module promoted from Staging to Production arrives in Production with its original configuration values intact, including any that are Staging-specific.

This article covers how to manage environment-specific values so modules behave correctly at every environment level.

What Does Not Transfer

The following are not copied or updated when a resource is promoted:

These must be configured independently in each environment. Verify them after every promotion.

Using Global Variables for Environment-Specific Values

The most common source of failures after promotion is hard-coded environment-specific values in modules. Examples include a hard-coded API endpoint, a Staging-specific feature flag value, or a configuration key that only exists in one environment.

The correct approach is to store environment-specific values as Global Variables. Global Variables are key-value pairs defined at the environment level. A module references the variable by key, and the environment resolves it to the correct value at runtime. For example, the same module reads API_BASE_URL in Staging and gets https://api-staging.example.com; in Production it gets https://api.example.com, with no change to the module itself.

Setting Up Global Variables

1. Identify every environment-specific value in the module: API endpoints, credentials, feature flags, identifiers.

2. Define each value as a Global Variable in Global Variables Administration with a consistent key name across all environments.

3. Replace hard-coded values in module configurations with the corresponding Global Variable key.

4. Verify the correct value is defined in each environment (Staging, QA, UAT, Production) before promoting.

Global Variables can be promoted between environments using the Promote action in Global Variables Administration, or set manually in each environment. If the value differs between environments, set them manually instead of promoting.

Managing Service Configuration

Services define how modules connect to external systems. A service configured in Staging might use a Staging API key and a Staging endpoint. The same service in Production must use Production credentials pointing at the Production system.

Configure each service independently in each environment. Do not promote Staging credentials to Production. After promoting a module that calls a service:

1. Open Services Administration in the target environment.

2. Verify the service exists and is configured with the correct credentials and endpoint for that environment.

3. Test the service connection before testing the module.

Managing SSO Configuration

SSO configurations are environment-specific. An SSO configuration in Staging does not transfer to Production during promotion. Each environment requires its own SSO setup with the identity provider.

After provisioning a new environment, configure SSO separately in SSO Management. Ensure the redirect URIs registered with the identity provider match the target environment's URL.

Common Pitfalls

Hard-Coded Endpoints

A module promoted with a hard-coded Staging API endpoint will call the Staging API from Production. The request might succeed (with wrong data) or fail silently. Replace all hard-coded endpoints with Global Variables before promotion.

Missing Global Variables

If a module references a Global Variable key that does not exist in the target environment, the module receives an empty value. The module might fail silently or produce incorrect output. Define all referenced Global Variable keys in every environment before promoting.

Service Credentials Not Updated

A service promoted or re-configured in Staging retains Staging credentials in Production unless explicitly updated. After any service configuration change in Staging, verify the Production service is configured with the correct Production credentials.

Configuration Changes After Promotion

Environment Administration settings (session timeouts, security policies, file limits) do not change when resources are promoted. If organizational policy requires different settings in Production, configure them directly in the Production environment's Environment Administration. These changes take effect immediately and do not require promotion.

Environment Configuration Reference

Run through this reference when setting up or auditing an environment after promotion.