diff options
| author | Rémy Coutable <remy@rymai.me> | 2017-07-07 02:34:51 +0200 |
|---|---|---|
| committer | Rémy Coutable <remy@rymai.me> | 2017-07-07 02:34:51 +0200 |
| commit | 97611c88fcbae6b025750e6ebf2061a3d87d9753 (patch) | |
| tree | 1d4ff635a807a49f99af219dc83c265a3465a4a6 /doc | |
| parent | 040eeb1039b4298ea56a670a0a4ae511288806d6 (diff) | |
| download | gitlab-ce-97611c88fcbae6b025750e6ebf2061a3d87d9753.tar.gz | |
Don't use Flipper for the Performance Bar
The implementation now simply rely on the
`performance_bar_allowed_group_id` Application Setting.
Signed-off-by: Rémy Coutable <remy@rymai.me>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/administration/monitoring/performance/performance_bar.md | 28 | ||||
| -rw-r--r-- | doc/development/feature_flags.md | 3 |
2 files changed, 1 insertions, 30 deletions
diff --git a/doc/administration/monitoring/performance/performance_bar.md b/doc/administration/monitoring/performance/performance_bar.md index 6ee21eae194..ee680c7b258 100644 --- a/doc/administration/monitoring/performance/performance_bar.md +++ b/doc/administration/monitoring/performance/performance_bar.md @@ -33,31 +33,3 @@ Make sure _Enable the Performance Bar_ is checked and hit  --- - -## Enable the Performance Bar via the API - -Under the hood, the Performance Bar activation is done via the `performance_bar` -[Feature Flag](../../../development/features_flags.md). - -That means you can also enable or disable it via the -[Features API](../../../api/features.md#set-or-create-a-feature). - -### For the `performance_team` feature group - -The `performance_team` feature group maps to the group specified in your [Admin -area](#enable-the-performance-bar-via-the-admin-panel). - -``` -curl --data "feature_group=performance_team" --data "value=true" --header "PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK" https://gitlab.example.com/api/v4/features/performance_bar -``` - -### For specific users - -It's also possible to enable the Performance Bar for specific users in addition -to a group, or even instead of a group: - -``` -curl --data "user=my_username" --data "value=true" --header "PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK" https://gitlab.example.com/api/v4/features/performance_bar -``` - -[reconfigure]: ../../restart_gitlab.md#omnibus-gitlab-reconfigure 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) |