From 3302e66ab1a7ecd6b21192238f6332d5fa873959 Mon Sep 17 00:00:00 2001 From: Thomas Heartman Date: Fri, 25 Feb 2022 09:10:22 +0100 Subject: [PATCH] docs: remove "future enhancements" section of environments doc These things are either implemented or just around the corner now. I suggest removing them to not be misleading anymore. Case in point: we just had a customer asking us when the permissions system would be ready because the docs say it's planned as a future improvement. --- website/docs/user_guide/environments.md | 10 ---------- 1 file changed, 10 deletions(-) diff --git a/website/docs/user_guide/environments.md b/website/docs/user_guide/environments.md index 029bcb8469a..35b721272cb 100644 --- a/website/docs/user_guide/environments.md +++ b/website/docs/user_guide/environments.md @@ -146,13 +146,3 @@ In order to support configuration per environment we had to rebuild our feature * **Unleash v4.2** will provide _early access_ to environment support. This means that it can be enabled per customer via a feature flag. * **Unleash v4.3** plans to provide general access to the environment support for all users of Unleash (Open-Source, Pro, Enterprise). - - -### Future enhancements - -With improved environment capabilities we have also done the groundwork to be able to also improve other related aspects inside Unleash: - - - -* Improve **Usage Metrics** to be able to show usage and evaluation results per hour for multiple days with dimensions such as environment, application and time (per hour). -* Improve **RBAC** with the ability to limit who can change configuration for a specific environment (planned as an enterprise feature).