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

Use absolute URL for intra-doc link.

Browse Source 
I don't know how this works in docusaurus 🤷
This commit is contained in:
Thomas Heartman 2021-11-11 15:41:54 +01:00
parent 8a41799731
commit 257497153c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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. 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](../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 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.
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. 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.