Fix Namespace list API for compliance framework
What does this MR do?
!54088 (merged) updated feature flag and license check for compliance_framework
attribute to namespace level. This change was made to support the enablement of the feature for individual namespaces in gitlab.com.
compliance_frameworks
attribute in Namespace list API is currently guarded by a global FF check.
This MR adds a resolver for compliance_framework
attribute and checks if the current user has the ability to admin
compliance frameworks in the namespace under consideration.
Screenshots (strongly suggested)
Before | After |
---|---|
![]() |
![]() |
Does this MR meet the acceptance criteria?
Conformity
- [-] Changelog entry Feature is gated
-
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
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
Edited by Aishwarya Subramanian