[Feature flag] Enable View the environment that generated the alert

What

Remove the :expose_environment_path_in_alert_details feature flag

Owners

  • Team: @gitlab-org/ci-cd/progressive-delivery
  • Most appropriate slack channel to reach out to: #g_progressive-delivery
  • Best individual to reach out to: @agulina

Expectations

What are we expecting to happen?

When the Feature Flag is remove, the Environment Path will be available and visible in the Alert Details. We expect the possible following 3 scenarios to happen:

A B C
environment is queried from graphQL environment is queried from graphQL environment is queried from graphQL but it's null for some reason
path is returned and it's a string path is null for some reason
The page has the environment displayed (in the table, environment is above details) The page looks as in B but the name of the environment is not a link The page will not display the environment in the summary but it will have an empty row in the table
Screenshot_2020-09-29_at_19.50.43 Screenshot_2020-09-30_at_18.33.16 Screenshot_2020-09-29_at_19.01.04

What might happen if this goes wrong?

What can we monitor to detect problems with this?

Beta groups/projects

If applicable, any groups/projects that are happy to have this feature turned on early. Some organizations may wish to test big changes they are interested in with a small subset of users ahead of time for example.

  • https://gitlab.com/gitlab-examples/ops/incident-setup/everyone/tanuki-inc/ project

Roll Out Steps

  • Enable on staging (/chatops run feature set expose_environment_path_in_alert_details true --staging)
  • Test on staging
  • Ensure that documentation has been updated
  • Enable on GitLab.com for individual groups/projects listed above and verify behaviour (/chatops run feature set --project=gitlab-org/gitlab expose_environment_path_in_alert_details true)
  • Coordinate a time to enable the flag with #production and #g_delivery on slack.
  • Announce on the issue an estimated time this will be enabled on GitLab.com
  • Enable on GitLab.com by running chatops command in #production (/chatops run feature set expose_environment_path_in_alert_details true)
  • Cross post chatops Slack command to #support_gitlab-com (more guidance when this is necessary in the dev docs) and in your team channel
  • Announce on the issue that the flag has been enabled
  • Remove feature flag and add changelog entry
  • After the flag removal is deployed, clean up the feature flag by running chatops command in #production channel
Edited by Angelo Gulina