[FF] new_ultimate_trial_endpoint -- Route Ultimate trial creation to new CustomersDot endpoint

Summary

Roll out the feature currently behind the new_ultimate_trial_endpoint feature flag.

• DRI: @syarynovskyi
• Team Slack channel: #g_acquisition

Note

Process and guidance live in the docs — this issue is just the commands and a place to track the rollout. "Rolling out" means incrementally enabling the flag on GitLab.com to validate stability — it is not the same as releasing the feature, which happens when the flag is removed. Feature flag controls · Feature flag lifecycle

What could go wrong?

If the new trials/gitlab_com/ultimates CustomersDot endpoint has a bug or is unavailable, users starting an Ultimate trial on GitLab.com would see trial creation fail. Watch CustomersDot's endpoint error rate and the GitLab.com trial-creation success rate on https://dashboards.gitlab.net before increasing rollout.

Rollout

Run all production /chatops in #production and cross-post the results to #g_acquisition. Background: incremental rollout process, feature actors.

Non-production

/chatops gitlab run feature set new_ultimate_trial_endpoint 50 --actors --dev --pre --staging --staging-ref
/chatops gitlab run feature set new_ultimate_trial_endpoint true --dev --pre --staging --staging-ref

Production — percentage rollout (wait ≥15 min between steps, watch dashboards):

/chatops gitlab run feature set new_ultimate_trial_endpoint <percentage> --actors

Or target specific actors instead:

/chatops gitlab run feature set --project=gitlab-org/gitlab,gitlab-org/gitlab-foss new_ultimate_trial_endpoint true
/chatops gitlab run feature set --group=gitlab-org,gitlab-com new_ultimate_trial_endpoint true
/chatops gitlab run feature set --user=syarynovskyi new_ultimate_trial_endpoint true

Before global rollout

Confirm the relevant gotchas before going to 100% — see enabling a feature for GitLab.com:

• Docs + version history updated
• Breaking changes announced, if any
• Change management issue opened, if required
• External API consumers handled with a fail-open mechanism, if applicable

Cleanup

Remove the flag once deemed stable — see cleaning up. Track it here, or open a follow-up Feature Flag Cleanup issue. Remove the flag and its YAML definition from the codebase, then:

/chatops gitlab run release check <merge-request-url> <milestone>
/chatops gitlab run feature delete new_ultimate_trial_endpoint --dev --pre --staging --staging-ref --production

Rollback

/chatops gitlab run feature set new_ultimate_trial_endpoint false                                         # production
/chatops gitlab run feature set new_ultimate_trial_endpoint false --dev --pre --staging --staging-ref     # non-production
/chatops gitlab run feature delete new_ultimate_trial_endpoint --dev --pre --staging --staging-ref --production  # remove entirely