Skip to content

Duo Landing Page - Adjust Routes to redirect to Duo Home

Lindsey Shelton requested to merge duo-lp-adjust-routes-groups into duo-lp-vue-components

What does this MR do and why?

The purpose of this MR is to adjust all previous duo subscription components to be redirected to use the new GitLab Duo home page. There is also an update to navigation to finally go directly to the GitLab Duo page as well with this MR.

Related Issues:

  • #493379 - Setup Duo Landing Page
  • #493957 - Duo Settings Page - Setup Seat Utilization Box

Related MRs:

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

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

THESE CHANGES ARE FOR GROUPS ONLY

Screen Recording
Screen_Recording_2024-10-16_at_9.06.48_PM

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

For frontend changes:

You will need an GitLab Ultimate license for these changes as well as a connection to CustomersDot. Also, make sure you have Duo set up with a group as indicated here.

In gitlab-development-kit

  • env.runit example
export GITLAB_SIMULATE_SAAS=1
export GITLAB_LICENSE_MODE=test
export LLM_DEBUG=1
export AI_GATEWAY_URL=http://0.0.0.0:5052
export CLOUD_CONNECTOR_SELF_SIGN_TOKENS=1
export CUSTOMER_PORTAL_URL=https://customers.staging.gitlab.com/
  • gdk.yml example to set up CDot
license:
  customer_portal_url: https://customers.staging.gitlab.com
  license_mode: test

Group - SaaS Instance

  1. Run GITLAB_SIMULATE_SAAS=1 gdk restart in your GDK.
  2. Go to Group > Settings > GitLab Duo.
  3. Validate page redirects to settings/-/gitlab_duo.

For backend changes:

Tests

  1. Run bundle exec rspec ee/spec/components/gitlab_subscriptions/discover_duo_pro_component_spec.rb
  2. Run bundle exec rspec ee/spec/features/gitlab_subscriptions/trials/duo_enterprise/creation_with_multiple_existing_namespace_flow_spec.rb
  3. Run bundle exec rspec ee/spec/features/gitlab_subscriptions/trials/duo_enterprise/creation_with_one_existing_namespace_flow_spec.rb
  4. Run bundle exec rspec ee/spec/features/gitlab_subscriptions/trials/duo_pro/creation_with_multiple_existing_namespace_flow_spec.rb
  5. Run bundle exec rspec ee/spec/features/gitlab_subscriptions/trials/duo_pro/creation_with_one_existing_namespace_flow_spec.rb
  6. Run bundle exec rspec ee/spec/features/gitlab_subscriptions/trials/creation_with_multiple_existing_namespace_flow_spec.rb
  7. Run bundle exec rspec ee/spec/features/gitlab_subscriptions/trials/creation_with_no_existing_namespace_flow_spec.rb
  8. Run bundle exec rspec ee/spec/features/gitlab_subscriptions/trials/creation_with_one_existing_namespace_flow_spec.rb
  9. Run bundle exec rspec ee/spec/requests/gitlab_subscriptions/trials/duo_enterprise_controller_spec.rb
  10. Run bundle exec rspec ee/spec/requests/gitlab_subscriptions/trials/duo_pro_controller_spec.rb
  11. Run bundle exec rspec ee/spec/requests/gitlab_subscriptions/trials/duo_pro_controller_spec.rb
  12. Run bundle exec rspec ee/spec/presenters/gitlab_subscriptions/trials/duo_pro_status_widget_presenter_spec.rb
Edited by Lindsey Shelton

Merge request reports