[Feature flag] Enable no_onboarding_enterprise_users

Current status - 2025-03-21

Fully enabled in production, confirmed ok in production, cleanup MR has merged and we are waiting for it to hit production before performing final closure steps.

Summary

This issue is to roll out the feature on production, that is currently behind the no_onboarding_enterprise_users 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?

Enterprise users will not be entered into onboarding on user creation.

What can go wrong and how would we detect it?

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 has been deployed to non-production environments with /chatops run auto_deploy status https://gitlab.com/gitlab-org/gitlab/-/merge_requests/182649
  • Enable the feature globally on non-production environments with /chatops run feature set no_onboarding_enterprise_users true
  • Verify user onboarding still works as expected by signing up for a new account and observing onboarding is unchanged.
  • If the feature flag causes end-to-end tests to fail, disable the feature flag on staging to avoid blocking deployments.
    • See #e2e-run-staging Slack channel and look for the following messages:
      • test kicked off: Feature flag no_onboarding_enterprise_users has been set to true on **gstg**
      • test result: This pipeline was triggered due to toggling of no_onboarding_enterprise_users 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.

Specific rollout on production

For visibility, all /chatops commands that target production must be executed in the #production Slack channel and cross-posted (with the command results) to the responsible team's Slack channel.

  • Ensure that the feature MRs have been deployed to both production and canary with /chatops run auto_deploy status https://gitlab.com/gitlab-org/gitlab/-/merge_requests/182649
  • Depending on the type of actor you are using, pick one of these options:
    • /chatops run feature set no_onboarding_enterprise_users true
  • Verify user onboarding still works as expected by signing up for a new account and observing onboarding is unchanged.

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.

Global rollout on production

For visibility, all /chatops commands that target production must be executed in the #production Slack channel and cross-posted (with the command results) to the responsible team's Slack channel.

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 to remove the no_onboarding_enterprise_users 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.
  • Close [the feature issue][#520498 (closed)] to indicate the feature will be released in the current milestone.
  • Once the cleanup MR has been deployed to production, clean up the feature flag from all environments by running these chatops command in #production channel: /chatops run feature delete no_onboarding_enterprise_users --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 no_onboarding_enterprise_users false
  • Disable the feature flag on non-production environments:
/chatops run feature set no_onboarding_enterprise_users false --dev --pre --staging --staging-ref
  • Delete feature flag from all environments:
/chatops run feature delete no_onboarding_enterprise_users --dev --pre --staging --staging-ref --production
Edited by Doug Stull