Create Group Usage Quotas menu entry in Core
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 |
|
Screenshots or screen recordings
SaaS
EE andUsage Quotas menu in both
FF off | FF on |
---|---|
![]() |
![]() |
EE unlicensed
- Removing your license in: http://gdk.test:3000/admin/subscription
FF off | FF on |
---|---|
![]() |
![]() |
CE
export FOSS_ONLY=1 && gdk restart
FF off | FF on |
---|---|
![]() |
![]() |
How to set up and validate locally
We need to validate this in 4 scenarios:
- GitLab EE: by having a test license in your GDK.
- GitLab SaaS: setup a license like the above and simulate SaaS
- GitLab EE Unlicensed: by removing your license in http://gdk.test:3000/admin/subscription
-
GitLab CE: by executing
export FOSS_ONLY=1
gdk restart
- 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.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Sheldon Led