mirror of
https://github.com/Unleash/unleash.git
synced 2024-11-01 19:07:38 +01:00
94bfb757d6
## What & why This update does three things: 1. Adjusts the environment cloning feature availability notice: because this has been released. 2. Updates the availability notice for environments (to conform with the standard docusaurus way of doing things): for consistency 3. Add a brief explanation of environment types: because this isn't documented anywhere ## Sources The note about how environment types work is sourced from this old [slack thread (internal to the team)](https://unleash-community.slack.com/archives/G01MU2Q49QC/p1659600175175769)
40 lines
2.0 KiB
Plaintext
40 lines
2.0 KiB
Plaintext
---
|
|
title: How to clone environments
|
|
---
|
|
|
|
:::info availability
|
|
|
|
Environment cloning was made available in Unleash 4.19.
|
|
|
|
:::
|
|
|
|
[Environment cloning](../reference/environments.md#cloning-environments) enables Unleash admins to duplicate existing environments, including all feature toggles strategies and their state.
|
|
|
|
## Step 1: Navigate to the environments page {#step-1}
|
|
|
|
Navigate to the _Environments_ page in the admin UI (available at the URL `/environments`). Use the navigation menu item "Configure" and select "Environments".
|
|
|
|
![The admin UI navigation "Configure" submenu with the Environments item highlighted.](/img/clone-environment-1.png)
|
|
|
|
## Step 2: Select an environment to clone {#step-2}
|
|
|
|
Select an environment to clone. On the right side, open the actions submenu and select "Clone".
|
|
|
|
![The "production" environment actions submenu with the Clone option highlighted.](/img/clone-environment-2.png)
|
|
|
|
## Step 3: Fill in the clone environment form {#step-3}
|
|
|
|
Give your new environment a name. The name must be unique and cannot be the same as the original environment. The name is pre-filled with a suggestion, but you can change it to whatever you like.
|
|
|
|
Select an environment type, which projects should have their environment configuration cloned, and whether to keep the existing user permissions for the new environment.
|
|
|
|
![The clone environment form filled with some example data, and the Clone environment button highlighted at the bottom.](/img/clone-environment-3.png)
|
|
|
|
You can optionally generate an API token for the new environment right away. Select which projects the token should have access to, and the token will be generated when you submit the form.
|
|
|
|
![The clone environment form with the API Token section highlighted and the Generate an API token now option selected](/img/clone-environment-4.png)
|
|
|
|
![The token details with the "Copy Token" element highlighted.](/img/clone-environment-5.png)
|
|
|
|
You can always create API tokens for the new environment by following the [_Generating an API token_](../how-to/how-to-create-api-tokens.mdx) guide.
|