mirror of
https://github.com/Unleash/unleash.git
synced 2024-12-22 19:07:54 +01:00
d5fbd0b743
## What This (admittedly massive) PR updates the "physical" documentation structure and fixes url inconsistencies and SEO problems reported by marketing. The main points are: - remove or move directories : advanced, user_guide, deploy, api - move the files contained within to the appropriate one of topics, how-to, tutorials, or reference - update internal doc links and product links to the content - create client-side redirects for all the urls that have changed. A number of the files have been renamed in small ways to better match their url and to make them easier to find. Additionally, the top-level api directory has been moved to /reference/api/legacy/unleash (see the discussion points section for more on this). ## Why When moving our doc structure to diataxis a while back, we left the "physical' files lying where they were, because it didn't matter much to the new structure. However, that did introduce some inconsistencies with where you place docs and how we organize them. There's also the discrepancies in whether urls us underscores or hyphens (which isn't necessarily the same as their file name), which has been annoying me for a while, but now has also been raised by marketing as an issue in terms of SEO. ## Discussion points The old, hand-written API docs have been moved from /api to /reference/api/legacy/unleash. There _is_ a /reference/api/unleash directory, but this is being populated by the OpenAPI plugin, and mixing those could only cause trouble. However, I'm unsure about putting /legacy/ in the title, because the API isn't legacy, the docs are. Maybe we could use another path? Like /old-docs/ or something? I'd appreciate some input on this.
40 lines
2.1 KiB
Plaintext
40 lines
2.1 KiB
Plaintext
---
|
|
title: How to clone environments
|
|
---
|
|
|
|
:::info availability
|
|
|
|
Environment cloning is an upcoming feature, and is scheduled to become available in one of the next few releases.
|
|
|
|
:::
|
|
|
|
[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".
|
|
|
|
|
|
|
|
## 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".
|
|
|
|
|
|
|
|
## 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.
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
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.
|