summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJob van der Voort <jobvandervoort@gmail.com>2018-02-14 12:40:06 +0000
committerJob van der Voort <jobvandervoort@gmail.com>2018-02-14 12:40:06 +0000
commit5e2c1778c26cb1f5dceb1eb5aeb64463e0f2a211 (patch)
tree5af6a5e15ba2c16850af6cec3dfef1416203c184
parent12447f12e0ec7bb026b385fc0695bcdca101ad61 (diff)
downloadgitlab-ce-5e2c1778c26cb1f5dceb1eb5aeb64463e0f2a211.tar.gz
clarify what kind of feature flags we support
-rw-r--r--doc/development/feature_flags.md7
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/development/feature_flags.md b/doc/development/feature_flags.md
index 59e8a087e02..5d1f657015c 100644
--- a/doc/development/feature_flags.md
+++ b/doc/development/feature_flags.md
@@ -1,6 +1,6 @@
# Manage feature flags
-Starting from GitLab 9.3 we support feature flags via
+Starting from GitLab 9.3 we support feature flags for features in GitLab via
[Flipper](https://github.com/jnunemaker/flipper/). You should use the `Feature`
class (defined in `lib/feature.rb`) in your code to get, set and list feature
flags.
@@ -19,3 +19,8 @@ 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)
+
+## Feature flags for user applications
+
+GitLab does not yet support the use of feature flags in deployed user applications.
+You can follow the progress on that [in the issue on our issue tracker](https://gitlab.com/gitlab-org/gitlab-ee/issues/779). \ No newline at end of file