## Overview Extract addon-related lead creation from the `trials_controller.rb#create_addon` method into a dedicated `Leads::GitlabCom::AddonsController` on CustomersDot, with corresponding routing changes on GitLab.com. ## Problem The `trials_controller.rb#create_addon` method currently handles both: 1. Creating a lead for the addon trial request 2. Applying the addon trial to the namespace This mixes lead generation concerns with trial application logic. We need to separate the lead creation into its own endpoint while keeping trial application in the trials controller. ## Scope **GitLab.com only** - This migration targets namespace-based subscriptions. This epic focuses solely on extracting the **lead creation** portion. Addon trial application will be handled in a separate epic. ## Implementation Plan ### Phase 1: CustomersDot - Create New Controller - Create `app/controllers/leads/gitlab_com/addons_controller.rb` - Extract addon-related lead creation logic from `trials_controller.rb#create_addon` - Add routes for new endpoint: `POST /leads/gitlab_com/addons` - Comprehensive test coverage ### Phase 2: GitLab.com - Add Feature Flag and Routing - Add feature flag: `new_addon_lead_endpoint` - Update GitLab.com code to call new lead endpoint before addon trial application - Add fallback to legacy flow when flag is disabled - Test both code paths ### Phase 3: Rollout (engineer to generate rollout issue during Phase 2) - Enable feature flag gradually (percentage-based rollout) - Monitor error rates and performance - Achieve 100% rollout ### Phase 4: Cleanup - Remove addon-related lead creation logic from `trials_controller.rb#create_addon` on CustomersDot - Remove feature flag and legacy routing from GitLab.com - Update any documentation in https://docs.gitlab.com/development/product_qualified_lead_guide/ ## Success Criteria - [ ] New `Leads::GitlabCom::AddonsController` deployed to CustomersDot production - [ ] GitLab.com routing updated with feature flag - [ ] Feature flag rolled out to 100% on GitLab.com - [ ] Legacy lead creation code removed from `trials_controller.rb#create_addon` - [ ] Addon trial application logic remains intact in `trials_controller.rb` - [ ] No regressions in addon-related lead creation - [ ] Test coverage maintained or improved ## Related - Parent Epic: https://gitlab.com/groups/gitlab-org/-/epics/20064 - Original discussion: https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/10425#note_2010275251