diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-20 15:26:25 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-07-20 15:26:25 +0300 |
commit | a09983ae35713f5a2bbb100981116d31ce99826e (patch) | |
tree | 2ee2af7bd104d57086db360a7e6d8c9d5d43667a /doc/development/feature_flags/controls.md | |
parent | 18c5ab32b738c0b6ecb4d0df3994000482f34bd8 (diff) |
Add latest changes from gitlab-org/gitlab@13-2-stable-ee
Diffstat (limited to 'doc/development/feature_flags/controls.md')
-rw-r--r-- | doc/development/feature_flags/controls.md | 13 |
1 files changed, 11 insertions, 2 deletions
diff --git a/doc/development/feature_flags/controls.md b/doc/development/feature_flags/controls.md index d4d1ec74591..9e7ce74cc0c 100644 --- a/doc/development/feature_flags/controls.md +++ b/doc/development/feature_flags/controls.md @@ -210,11 +210,20 @@ actors. Feature.enabled?(:some_feature, group) ``` -NOTE: - +NOTE: **Note:** **Percentage of time** rollout is not a good idea if what you want is to make sure a feature is always on or off to the users. In that case, **Percentage of actors** rollout is a better method. +Lastly, to verify that the feature is deemed stable in as many cases as possible, +you should fully roll out the feature by enabling the flag **globally** by running: + +```shell +/chatops run feature set some_feature true +``` + +This changes the feature flag state to be **enabled** always, which overrides the +existing gates (e.g. `--group=gitlab-org`) in the above processes. + ### Feature flag change logging Any feature flag change that affects GitLab.com (production) will |