Development, staging, and production tenant environments
Each Identity Cloud account includes a development, a staging, and a production tenant environment. These three environments let you build, test, and deploy your IAM applications:
| Tenant Environment | Description |
|---|---|
Development |
Used for building and adding new features. |
Staging |
Used for testing development changes, including stress tests and scalability tests with realistic deployment settings. |
Production |
Used for deploying applications into operation for end users. |
Promoting configuration
Identity Cloud uses a promotion model to move configuration changes through the three environments.
The development environment is mutable. This means that you can make configuration changes to the environment through one of the admin UIs or through the REST API.
By contrast, the staging and production environments are not mutable. This means that you cannot make configuration changes to these environments directly. Instead, you must move the changes from the development environment to the staging environment by running a promotion, then move the changes from the staging environment to the production environment by running a further promotion.
In situations where you want a configuration value (such as an authentication token) to be distinct in each environment, you can set the value as an ESV in each environment, then insert the ESV placeholder into your configuration, then move the configuration to your staging and production environments by running sequential promotions. Refer to Use ESVs in configuration placeholders.
| Tenant Environment | Mutable | Make Configuration Changes |
|---|---|---|
Development |
||
Staging |
||
Production |