Understanding environments

An environment is the named target a CloudRadial AutomationAI deployment runs against. This article explains what an environment is, how you set it when creating a deployment, and how it scopes a deployment. It is for Admin and Owner roles.

• What an Environment Is
• Setting the Environment on a Deployment
• How the Environment Scopes a Deployment

What an Environment Is

An environment is a label you give a deployment to name the target it runs against — for example prod or staging. It is part of what a deployment binds together, alongside the published workflow version and the runner. The environment lets you tell apart deployments of different workflows at a glance in the Deployments grid, where it appears in its own column.

Setting the Environment on a Deployment

You set the environment when you create a deployment. Open Deployments, click Deploy, and fill in the Environment field along with the workflow, published version, and runner. The field defaults to prod and accepts up to 64 characters. The environment is fixed for the life of the deployment: editing a deployment lets you change its version or runner, but not its environment label.

How the Environment Scopes a Deployment

The environment names where a deployment runs. Each deployment carries one environment label, and it stays with that deployment through every run — the runs in History belong to the deployment, so they inherit its environment. To run the same workflow against a different environment, edit the deployment to point at the appropriate runner for that target, since a workflow has one active deployment at a time.