Create and Configure OneCloud Environment

Environments are used to manage the lifecycle of OneCloud Chains. Chains can be promoted between Environments, and Workspace Variables can be set per environment and override the default value.

🌟 Best Practice

Notice the image below, with a development, test, and production Environment. Use different Environments to build and test your chain. When a development chain is ready, promote it to the production Environment.

Add an Environment

  • Select Workspaces from the left-navigation panel.

  • In the desired Workspace, click the plus button (+) next to any existing Environments

  • The Environment Configuration window will be launched.

📓 The order of the Environments currently cannot be changed.

Environment Configuration

Similar to the Workspace editor, the Environment editor asks for basic information about the Environment that is being created. The interface also provides the capability to override values for the variables that have been set at a Workspace level and to set a color for the Environment.

📓 The Environment name and color will be visible in the upper left-hand corner of every page to provide a visual cue to all users working in a particular Environment.

Edit an Existing Environment

  • Click the pencil icon next to the Environment's name to make changes.

💥 Deleting a Environment is Irreversible

Not even OneCloud Support can restore deleted objects. Deleting an Environment cannot happen by chance as the action requires a three-step process. Users must confirm their desire to delete an Environment by: 1) Clicking delete when editing an Environment; 2) Type D-E-L-E-T-E; and 3) Clicking delete once more.

Override an Environment Variable

Variables have a priority order and can be overrode when being used. As you have seen in the above screenshots, Workspace variables are also Environment variables. This is for a couple reasons:

  • That is due to the concept of Lifecycle Management procedures. A value of a variable in DEV may not be the same value as the variable in PROD.

  • You may want to execute a run of the chains with a different value for a single execution than the defaults (override concept).

For that reason there is a priority order when the variables are being used. If no value is specified for a variable at the Environment level then the value at the Workspace level is retrieved.

📚 Related Topics:

Chain Management

Workspace Configuration

Did this answer your question?