Clone an environment

Cloning lets you branch off a verified configuration instead of building one from scratch. It copies the rule configuration and variable overrides of an existing environment version into a new environment, and reuses the same origins. The clone starts as version 1 in a draft state, so you can keep editing until you activate.

🚧

Beta limitation

During beta, each workspace can have only one production environment, so you can clone only into a development or testing environment.

How to

Follow these steps to clone an environment.

1. From the Control Center menu, click Content delivery > CDN > Delivery Manager.

2. In the Workspaces page, click the workspace that contains the environment you want to clone.

3. Go to the Environments tab, and click the environment you want to clone.

4. In the environment version page, click Clone. The Clone environment screen opens.

5. In Source environment, select the version to clone from. You can clone either a draft or an active version. The source environment itself is the one you started from and can't be changed here.

6. In New environment, select an environment profile:

   • Development for short-lived, header-routed work that auto-deactivates after 30 days.
   • Testing for a persistent environment used for regression sweeps, load testing, and pre-production validation.

   The profile determines which networks your clone can activate on, how long it persists, and how its service hostnames are routed. See Environment profiles.

7. Enter an environment name.

8. Optionally, add a description.

9. In Routing, review how your clone handles the service hostname sets currently routed to your source environment. What you see depends on the profile you chose:

   • If you chose Development: the clone creates a header-based route for each set currently routed to your source environment, so you can test without affecting the service hostnames your source environment serves. Under New routes, leave a set switched on to create a new route, or switch it off to leave that set unrouted. Each set you leave on gets a new version that activates alongside your new environment.
   • If you chose Testing: routing starts empty and no existing set points to your clone. Under Service hostname sets routing to source, you can see which sets continue pointing to your source environment. To receive traffic, create host-based routes after cloning: route new service hostname sets, or reassign existing ones. See Add a route.

10. In Variable overrides, choose how your clone handles variables. Leave Copy variable overrides from source switched on to copy every override from the source environment, or switch it off to reset all variable values to their workspace defaults. See Override workspace variables.

11. In Clone summary, review Cloned objects: routed service hostname sets, variable overrides, origins, and rule sets.

12. Click Clone environment. You land on your new environment overview at draft version 1.

Next steps

1. If you copied variable overrides, review them on the Variables tab. Confirm you aren't exposing sensitive data in a less restricted environment, and add new overrides where a value needs to differ.
2. Finalize your rule configuration. See Delivery Manager Rules for details on available features and business logic implementation.
3. Review your routes. A development clone creates new versions of the routed service hostname sets, which you can edit before activation. A testing clone starts unrouted, so you need to route new or existing sets to it. See Add a route.
4. Activate and test your new environment and its routed service hostname sets.