Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2025-02-04 00:18:01 +01:00
Code Issues Projects Releases Wiki Activity

docs: simplify language + pre-configure -> preconfigure

Browse Source
This commit is contained in:
Thomas Heartman 2021-11-12 08:25:55 +01:00
parent 257497153c
commit b776984187
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/docs/user_guide/environments.md
View File

@ -15,7 +15,7 @@ title: Environments
Environments is a new way to organize activation strategy configurations for feature toggles into separate environments. In Unleash, a feature lives across all your environments — after all, the goal is to get the new feature released as soon as possible — but it makes sense to configure the activation differently per environment. You might want the feature enabled for everyone in development, but only for yourself in production, for instance.
Previously, Unleash Enterprise users have been able to leverage [strategy constraints](https://docs.getunleash.io/advanced/strategy_constraints) to control the rollout across environments. With the new environments feature, this is no longer necessary. Now all activation strategies belong to an explicit environment instead.
Previously, Unleash Enterprise could use [strategy constraints](https://docs.getunleash.io/advanced/strategy_constraints) to control the rollout across environments. With the new environments feature, this is no longer necessary. Now all activation strategies belong to an explicit environment instead.
Further, connected applications will use environment-scoped API keys to make sure they only download feature toggle configurations for the environment they are running in.
@ -110,7 +110,7 @@ In order to support configuration per environment we had to rebuild our feature
* Will get access to two pre-configured environments: “development” and “production”. Existing users of Unleash will also get an additional “default” environment to simplify adoption of environments.
* Will get access to two preconfigured environments: “development” and “production”. Existing users of Unleash will also get an additional “default” environment to simplify the adoption of environments.
* Will be possible to turn environments on/off for all projects.
@ -118,7 +118,7 @@ In order to support configuration per environment we had to rebuild our feature
* Will get access to two pre-configured environments: “development” and “production”. Existing users of Unleash will also get an additional “default” environment to simplify the adoption of environments.
* Will get access to two preconfigured environments: “development” and “production”. Existing users of Unleash will also get an additional “default” environment to simplify the adoption of environments.
* Will be possible to turn environments on/off for the default project.
@ -126,7 +126,7 @@ In order to support configuration per environment we had to rebuild our feature
* Will get access to two pre-configured environments: “development” and “production”. Existing users of Unleash will also get an additional “default” environment to simplify the adoption of environments.
* Will get access to two preconfigured environments: “development” and “production”. Existing users of Unleash will also get an additional “default” environment to simplify the adoption of environments.
* Will be possible to turn environments on/off for all projects
* Will be allowed to update and remove environments.
* Will be allowed to create new environments.