Skip to content

Check the Value of seat_control for User Cap Enforcement

Jason Goodman requested to merge check-seat-control-for-user-cap into master

What does this MR do and why?

Check the value of seat_control for user cap enforcement instead of the value of new_user_signups_cap.

We are switching the User Cap UI for gitlab.com groups to a new Seat Control UI. The current UI has just a single field, the new_user_signups_cap. The new UI will have a radio button (seat_control) with two values (off and user_cap) and the new_user_signups_cap field. We have code in production that sets the value of seat_control to user caps or off based on the value of the new_user_signups_cap field.

In this MR, we start looking at the value of seat_control to decide whether or not the User Cap is enabled. In a future MR, we will switch to the new Seat Control UI and expose the seat_control radio button to the user. At this point, we will also remove the code that changes the value of seat_control based on new_user_signups_cap.

This MR is step 5 of the development notes here: https://gitlab.com/gitlab-org/gitlab/-/issues/470094#note_1977685205

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/470094

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.

Edited by Jason Goodman

Merge request reports