Move subscriptions/hand_raise_leads_controller to gitlab_subscriptions
We want to consolidate our namespace/bounded context strategy around gitlab_subscriptions
.
- Move
ee/app/controllers/subscriptions/hand_raise_leads_controller.rb
toee/app/controllers/gitlab_subscriptions/hand_raise_leads_controller.rb
and use theGitlabSubscriptions
namespace. - Move
ee/app/helpers/subscriptions/hand_raise_leads_helper.rb
toee/app/helpers/gitlab_subscriptions/hand_raise_leads_helper.rb
and use theGitlabSubscriptions
namespace. - Move the routing definition from
ee/config/routes/subscription.rb
toee/config/routes/gitlab_subscriptions.rb
.- We want to eventually change the URL here as it isn't customer facing, only UI facing. However to do that we'll need to duplicate the route instead of replacing it first so that we don't encounter a case of a hand raise lead being dropped if submitting from a stale UI to the backend. Do that we may need to do something like this:
- create a new entry for the moved controller under
resource :gitlab_subscriptions
inee/config/routes/gitlab_subscriptions.rb
. - route the old route in
ee/config/routes/subscription.rb
to the new controller location. - release this MR and ensure it gets deployed to production.
- Wait a few days...
- Submit another MR to remove the old route in
ee/config/routes/subscription.rb
- create a new entry for the moved controller under
- We want to eventually change the URL here as it isn't customer facing, only UI facing. However to do that we'll need to duplicate the route instead of replacing it first so that we don't encounter a case of a hand raise lead being dropped if submitting from a stale UI to the backend. Do that we may need to do something like this:
Edited by Doug Stull