Skip to content

[Feature flag] Enable premium_can_trial_again

Summary

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

Premium namespaces will be able to apply for an ultimate trial if they previously had a trial while free.

What can go wrong and how would we detect it?

Eligible namespaces will not be able to apply for a trial(regression). We will validate manually.

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/174779
  • Verify a premium namespace that previously trialed while free can not apply for a trial through /-/trials/new
  • Enable the feature globally on non-production environments with /chatops run feature set premium_can_trial_again true --dev --pre --staging --staging-ref
  • Verify a premium namespace that previously trialed while free can apply for a trial through /-/trials/new
  • Verify no regressions:
    • Verify a premium namespace that did not previously trial can apply for a trial through /-/trials/new
    • Verify a free namespace that did not previously trial can apply for trial through /-/trials/new
  • 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 premium_can_trial_again has been set to true on **gstg**
      • test result: This pipeline was triggered due to toggling of premium_can_trial_again 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.
  • Ensure that documentation exists for the feature, and the version history text has been updated.

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.

  • Roll out the feature on production.
    • Example: /chatops run feature set premium_can_trial_again true.
  • Validate the feature using steps similar to the staging rollout steps above.
  • After the feature has been 100% enabled, wait for at least one day before releasing the feature.

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 premium_can_trial_again 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 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 premium_can_trial_again --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 premium_can_trial_again false
  • Disable the feature flag on non-production environments:
/chatops run feature set premium_can_trial_again false --dev --pre --staging --staging-ref
  • Delete feature flag from all environments:
/chatops run feature delete premium_can_trial_again --dev --pre --staging --staging-ref --production
Edited by Doug Stull