Add free user cap to read_only qualification for a namespace
What does this MR do and why?
- Adds free user cap being over as a qualification for setting a namespace in
read_only
state as per #372196 - Adds caching concept to the
over_limit?
free user enforcement in order to ensure we are performant per each request, but also exact by only applying this to the method invoked by policies.
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.
Related to #372196
Edited by Doug Stull