From 97611c88fcbae6b025750e6ebf2061a3d87d9753 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?R=C3=A9my=20Coutable?= Date: Fri, 7 Jul 2017 02:34:51 +0200 Subject: Don't use Flipper for the Performance Bar MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The implementation now simply rely on the `performance_bar_allowed_group_id` Application Setting. Signed-off-by: Rémy Coutable --- doc/development/feature_flags.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'doc/development') diff --git a/doc/development/feature_flags.md b/doc/development/feature_flags.md index a51adcfbd3f..59e8a087e02 100644 --- a/doc/development/feature_flags.md +++ b/doc/development/feature_flags.md @@ -15,8 +15,7 @@ Starting from GitLab 9.4 we support feature groups via Feature groups must be defined statically in `lib/feature.rb` (in the `.register_feature_groups` method), but their implementation can obviously be -dynamic (querying the DB etc.). You can see how the `performance_team` feature -group for a concrete example. +dynamic (querying the DB etc.). Once defined in `lib/feature.rb`, you will be able to activate a feature for a given feature group via the [`feature_group` param of the features API](../api/features.md#set-or-create-a-feature) -- cgit v1.2.1