Configure environments

Set the variables and secrets your application needs in each environment. For example, staging can use a test order service while production uses the live service.

Choose the environment

In your project, open Environments and select the environment you intend to change. Check the selection before adding values, especially when the project has both staging and production.

Identify the exact variable names required by the application or integration. The integration setup page lists names for external services. Project code defines its own settings.

Add the settings

Add each variable or secret using its required name. For example, an application that reads ORDER_SERVICE_URL needs that exact name, not a display label such as “Order service.”

Use test endpoints and credentials for staging. Use production credentials only in the production environment.

Save the configuration. Keep secret values in the environment's secret storage rather than in project source, chat messages, or shared examples.

Apply the change

In Deployments, confirm which deployment uses the environment. Redeploy when the runtime needs a fresh configuration snapshot.

Verify through behavior

Exercise one operation that depends on the setting. For a service endpoint, run a lookup and confirm it reaches the intended test or live service.

If the operation reports a missing variable, check its spelling, the selected environment, and whether the runtime has been refreshed. Use Logs to inspect the failure without printing the secret value itself.

Next