diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-08 03:05:58 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-11-08 03:05:58 +0300 |
commit | 1adb4373ba840a9bc771a8c9196f7183fd98b2b8 (patch) | |
tree | 1d319351302054fb1ca2223ed4da467fb2078765 /doc/development/feature_flags | |
parent | c324100967bbdd3f2f0ca3406c9261d35e69f148 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/development/feature_flags')
-rw-r--r-- | doc/development/feature_flags/controls.md | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/development/feature_flags/controls.md b/doc/development/feature_flags/controls.md index f22c3bb1e37..cbbbe1cd5ea 100644 --- a/doc/development/feature_flags/controls.md +++ b/doc/development/feature_flags/controls.md @@ -29,6 +29,14 @@ Monitor stage, Health group. For all production environment Chatops commands, use the `#production` channel. +Regardless of the channel in which the Chatops command is ran, any feature flag change that affects GitLab.com will automatically be logged in an issue. + +The issue is created in the [gl-infra/feature-flag-log](https://gitlab.com/gitlab-com/gl-infra/feature-flag-log/issues?scope=all&utf8=%E2%9C%93&state=closed) project, and it will at minimum log the Slack handle of person enabling a feature flag, the time, and the name of the flag being changed. + +The issue is then also posted to GitLab Inc. internal [Grafana dashboard](https://dashboards.gitlab.net/) as an annotation marker to make the change even more visible. + +Changes to the issue format can be submitted in the [Chatops project](https://gitlab.com/gitlab-com/chatops). + ## Rolling out changes When the changes are deployed to the environments it is time to start |