[Feature flag] Enable use_registration_type_db_value

Summary

This issue is to roll out the feature on production, that is currently behind the use_registration_type_db_value feature flag.

Owners

  • Most appropriate Slack channel to reach out to: #g_acquisition
  • Best individual to reach out to: @dstull

Expectations

What are we expecting to happen?

use of database values for knowledge of registration type during user onboarding

What can go wrong and how would we detect it?

Users may get into the wrong registration type during onboarding.

Rollout Steps

Note: Please make sure to run the chatops commands in the Slack channel that gets impacted by the command.

Rollout on non-production environments

  • Verify the MR with the feature flag is merged to master and have been deployed to non-production environments with /chatops run auto_deploy status <merge-commit-of-your-feature>
  • Enable the feature globally on non-production environments with /chatops run feature set use_registration_type_db_value true --dev --pre --staging --staging-ref
  • Verify that the feature works as expected. The best environment to validate the feature in is staging-canary as this is the first environment deployed to. Make sure you are configured to use canary.
  • If the feature flag causes end-to-end tests to fail, disable the feature flag on staging to avoid blocking deployments.
    • See #qa-staging Slack channel and look for the following messages:
      • test kicked off: Feature flag <feature-flag-name> has been set to true on **gstg**
      • test result: This pipeline was triggered due to toggling of <feature-flag-name> feature flag

For assistance with end-to-end test failures, please reach out via the #test-platform Slack channel. Note that end-to-end test failures on staging-ref don't block deployments.

Preparation before global rollout

  • Set a milestone to this rollout issue to signal for enabling and removing the feature flag when it is stable.
  • 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.
  • Notify your team channel (more guidance when this is necessary in the dev docs).

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 (#<slack-channel-of-dri-team>).

Release the feature

After the feature has been deemed stable, the clean 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 or use the checklist below in this same issue.

  • Create a merge request(!148595 (merged)) to remove the use_registration_type_db_value feature flag. Ask for review/approval/merge as usual. The MR should include the following changes:
    • Remove all references to the feature flag from the codebase.
    • Remove the YAML definitions for the feature from the repository.
    • Create a changelog entry.
  • Clean up the feature flag from all environments by running these chatops command in #production channel: /chatops run feature delete use_registration_type_db_value --dev --pre --staging --staging-ref --production
  • Close this rollout issue.

Rollback Steps

  • This feature can be disabled on production by running the following Chatops command:
/chatops run feature set use_registration_type_db_value false
  • Disable the feature flag on non-production environments:
/chatops run feature set use_registration_type_db_value false --dev --pre --staging --staging-ref
  • Delete feature flag from all environments:
/chatops run feature delete use_registration_type_db_value --dev --pre --staging --staging-ref --production
Edited by Doug Stull