Create Group Usage Quotas menu entry in Core

Sheldon Ledrequested to merge
led/371820-move-usage-quotas-menu-entry into master

What does this MR do and why?

This is a follow up on !102906 (merged) and last MR for #371820 (closed). This creates a menu entry for Usage Quotas Page in all GitLab Editions.

MR Cadence

Description MR
Move :read_usage_quotas policy to Core app !103021 (merged)
Create Usage Quotas route/controller/view in Core !102906 (merged)
Add menu entry on sidebar 👈 you're here

Screenshots or screen recordings

EE and SaaS

Usage Quotas menu in both

FF off FF on
usage_quotas_menu_ee_ff_off usage_quotas_menu_ee_ff_on

EE unlicensed

FF off FF on
usage_quotas_menu_eeu_ff_off.png usage_quotas_menu_eeu_ff_on

CE

export FOSS_ONLY=1 && gdk restart
FF off FF on
usage_quotas_menu_ce_ff_off usage_quotas_menu_ce_ff_on

How to set up and validate locally

We need to validate this in 4 scenarios:

  1. GitLab EE: by having a test license in your GDK.
  2. GitLab SaaS: setup a license like the above and simulate SaaS
  3. GitLab EE Unlicensed: by removing your license in http://gdk.test:3000/admin/subscription
  4. GitLab CE: by executing
    1. export FOSS_ONLY=1
    2. gdk restart
    3. Tanuki gdk website icon (the one in the browser tab) should be blue, then you're in CE

Now go to any Group Usage Quotas: http://gdk.test:3000/groups/flightjs/-/usage_quotas and check if your local setup matches the screenshots.

  • To enable the FF: Feature.enable(:usage_quotas_for_all_editions)
  • To disable the FF: Feature.enable(:usage_quotas_for_all_editions)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Sheldon Led

Merge request reports