Update redirect add_duo_pro url to include saas
What does this MR do and why?
Solves https://gitlab.com/gitlab-org/gitlab/-/issues/442670
We updated some areas of subscription_portal_add_duo_pro_seats_url
to subscription_portal_add_sm_duo_pro_seats_url
when a new route was introduced for the SM flow. We should update rest of the areas of subscription_portal_add_duo_pro_seats_url
to subscription_portal_add_saas_duo_pro_seats_url
so it is clear.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
How to set up and validate locally
General setup
Enable the following feature flags in the Rails console (bundle exec rails c
):
Feature.enable(:code_suggestions)
Feature.enable(:code_suggestions_tokens_api)
Feature.enable(:purchase_code_suggestions)
Feature.enable(:self_managed_code_suggestions)
Feature.enable(:hamilton_seat_management)
The following feature flags are needed on the Customers App:
- Setup and start CustomersDot (optional for last step)
- Create or locate a group that is not Free and has duo pro seats.
- Visit
http://localhost:3000/groups/<GROUP_NAME_ABOVE>/-/usage_quotas#code-suggestions-usage-tab
. - You should see the
Duo Pro
tab and "Add seats" button appear. - When you click the button, it should take you to CDot to purchase more Duo pro seats. (optional, can be skipped and we just confirm that the url redirect is still
http://localhost:5000/gitlab/namespaces/<GROUP_ID>/duo_pro_seats
)
Related to #442670