<!-- Title suggestion: [Feature flag] Enable description of feature --> ## Summary This issue is to rollout [the feature](https://gitlab.com/gitlab-org/gitlab/-/issues/363635) on production, that is currently behind the `slack_events_app_home_opened` feature flag. <!-- Short description of what the feature is about and link to relevant other issues. --> ## Owners - Team: ~"group::integrations" - Most appropriate slack channel to reach out to: `#g_ecosystem_integrations` - Best individual to reach out to: `@.luke` - PM: `@g.hickman` ## Expectations ### What are we expecting to happen? Unfortunately we can't actually test this on SaaS before enabling, as to test it requires our GitLab Slack App to be republished to the Slack app directory, and once that happens the feature is live for everyone. Instead, we'll need to QA on staging and then enable on production. ### When is the feature viable? Immediately. ### What might happen if this goes wrong? The API endpoint `/api/v4/integrations/slack/events` might error. This endpoint is only used by the Slack Events API. The GitLab Slack App's Home tab will not display our intended view, although the customer will not see any errors. Just a place-holder view provided by Slack. ### What can we monitor to detect problems with this? Sentry for errors. Kibana to see the worker. ### What can we check for monitoring production after rollouts? Sentry for errors. Kibana to see the worker. ## Rollout Steps ### Rollout on non-production environments - Ensure that the feature MRs have been deployed to non-production environments. - [x] `/chatops run auto_deploy status <merge-commit-of-your-feature>` - [x] Enable the feature globally on non-production environments. - [x] `/chatops run feature set slack_events_app_home_opened true --dev --staging --staging-ref` - [x] Verify that the feature works as expected. Posting the QA result in this issue is preferable. The best environment to validate the feature in is [staging-canary](https://about.gitlab.com/handbook/engineering/infrastructure/environments/#staging-canary) as this is the first environment deployed to. Note you will need to make sure you are configured to use canary as outlined [here](https://about.gitlab.com/handbook/engineering/infrastructure/environments/canary-stage/) when accessing the staging environment in order to make sure you are testing appropriately. ### Specific rollout on production The feature flag does not take an actor so there is no rollout. ### Preparation before global rollout - [x] Check if the feature flag change needs to be accompanied with a [change management issue](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#feature-flags-and-the-change-management-process). Cross link the issue here if it does. - [x] Ensure that you or a representative in development can be available for at least 2 hours after feature flag updates in production. If a different developer will be covering, or an exception is needed, please inform the oncall SRE by using the `@sre-oncall` Slack alias. - [x] Ensure that documentation has been updated ([More info](https://docs.gitlab.com/ee/development/documentation/feature_flags.html#features-that-became-enabled-by-default)). - [x] Announce on [the feature issue](https://gitlab.com/gitlab-org/gitlab/-/issues/363635) an estimated time this will be enabled on GitLab.com. - [x] Ensure that any breaking changes have been announced following the [release post process](https://about.gitlab.com/handbook/marketing/blog/release-posts/#deprecations-removals-and-breaking-changes) to ensure GitLab customers are aware. - [x] Notify `#support_gitlab-com` and your team channel ([more guidance when this is necessary in the dev docs](https://docs.gitlab.com/ee/development/feature_flags/controls.html#communicate-the-change)). ### Global rollout on production For visibility, all `/chatops` commands that target production should be executed in the `#production` slack channel and cross-posted (with the command results) to the responsible team's slack channel (`#g_TEAM_NAME`). - [x] [Incrementally roll out](https://docs.gitlab.com/ee/development/feature_flags/controls.html#process) the feature. - If the feature flag in code has [an actor](https://docs.gitlab.com/ee/development/feature_flags/#feature-actors), perform **actor-based** rollout. - [x] `/chatops run feature set slack_events_app_home_opened <rollout-percentage> --actors` - If the feature flag in code does **NOT** have [an actor](https://docs.gitlab.com/ee/development/feature_flags/#feature-actors), perform time-based rollout (**random** rollout). - [x] `/chatops run feature set slack_events_app_home_opened <rollout-percentage> --random` - Enable the feature globally on production environment. - [x] `/chatops run feature set slack_events_app_home_opened true` - [x] Announce on [the feature issue](https://gitlab.com/gitlab-org/gitlab/-/issues/363635) that the feature has been globally enabled. - [x] Wait for [at least one day for the verification term](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release). ### Release the feature After the feature has been [deemed stable](https://about.gitlab.com/handbook/product-development-flow/feature-flag-lifecycle/#including-a-feature-behind-feature-flag-in-the-final-release), the [clean up](https://docs.gitlab.com/ee/development/feature_flags/controls.html#cleaning-up) should be done as soon as possible to permanently enable the feature and reduce complexity in the codebase. You can either [create a follow-up issue for Feature Flag Cleanup](https://gitlab.com/gitlab-org/gitlab/-/issues/new?issuable_template=Feature%20Flag%20Cleanup) or use the checklist below in this same issue. <!-- The checklist here is to help stakeholders keep track of the feature flag status --> - [x] Create a merge request to remove `slack_events_app_home_opened` feature flag. Ask for review and merge it. - [x] Remove all references to the feature flag from the codebase. - [x] Remove the YAML definitions for the feature from the repository. - [x] Create [a changelog entry](https://docs.gitlab.com/ee/development/feature_flags/#changelog). - [x] Ensure that the cleanup MR has been included in the release package. If the merge request was deployed before [the monthly release was tagged](https://about.gitlab.com/handbook/engineering/releases/#self-managed-releases-1), the feature can be officially announced in a release blog post. - [x] `/chatops run release check <merge-request-url> <milestone>` - [x] Close [the feature issue](https://gitlab.com/gitlab-org/gitlab/-/issues/363635) to indicate the feature will be released in the current milestone. - [x] If not already done, clean up the feature flag from all environments by running these chatops command in `#production` channel: - [x] `/chatops run feature delete slack_events_app_home_opened --dev --staging --staging-ref --production` - [x] Close this rollout issue. ## Rollback Steps - [ ] This feature can be disabled by running the following Chatops command: ``` /chatops run feature set slack_events_app_home_opened false ```