## Summary Add feature flag and routing logic on GitLab.com to support the new `trials/gitlab_com/addons` endpoint on CustomersDot. ## Problem GitLab.com currently routes addon trial application to the legacy `trials_controller.rb` endpoint on CustomersDot. We need to add a feature flag to gradually migrate to the new dedicated endpoint. ## Prerequisites - [x] CustomersDot issue completed: New `Trials::GitlabCom::AddonsController` deployed to production - [ ] New endpoint verified working in CustomersDot staging ## Implementation Details ### Feature Flag **Name:** `new_addon_trial_endpoint` **Type:** `gitlab_com_derisk` (percentage-based rollout) **Default:** `false` - [ ] Create a feature flag rollout issue following https://docs.gitlab.com/development/feature_flags/#create-a-new-feature-flag - [ ] Add the issue to the current epic ### Code Changes **Locate addon trial application code:** - Find where GitLab.com calls CustomersDot for addon trials (Duo Pro, Duo Enterprise) - Likely in a service, helper, or controller **Add conditional routing:** ```ruby def addon_trial_url if Feature.enabled?(:new_addon_trial_endpoint) \"#{subscription_portal_url}/trials/gitlab_com/addons\" else \"#{subscription_portal_url}/trials/addon\" # Legacy endpoint end end ``` ## Rollout Plan This issue creates the feature flag infrastructure. Actual rollout will be handled in a separate rollout issue following GitLab's feature flag rollout process. ## Related - Parent Epic: https://gitlab.com/groups/gitlab-org/-/epics/20107