Expose a `removable` attribute for BillableMembers
What does this MR do?
In order for the frontend to clarify the membership type of a billable member and the actions that can be performed on them (e.g. removing), firstly we added a new attribute called membership_type in !60600 (merged).
Now in this MR we expose another attribute, removable, which uses the membership_type to establish if a billable member can be removed from the given group.
Removal of a billable member for a group is only possible for non-shared members (group and project members).
Shared members cannot be indivually removed - either the shared group needs to be removed entirely, or the shared group they actually belong to needs to remove that member.
Refs #325412 (closed)
Does this MR meet the acceptance criteria?
Conformity
-
I have included a changelog entry, or it's not needed. (Does this MR need a changelog?) -
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Security
Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team