Add compliance framework project labels to Projects API

Problem to solve

In %12.10 we introduced a compliance framework labeling feature for projects to support compliance-minded organizations in identifying regulated versus unregulated projects. This is helpful for customers relying on in-app experiences but does not adequately support customers relying on GitLab APIs for their operational purposes.

This particular feature is not currently supported by the Projects API, which would be beneficial to customers currently leveraging that API.

Intended users

• Sidney (Systems Administrator)
• The stakeholders managing a compliance program for GitLab -> Compliance Persona UX Research

Further details

Many customers rely on GitLab APIs to build or supplement custom, internal tooling for data collection, aggregation, and analysis.

Proposal

Include a project's compliance framework label (Image below) in the response object for the get single project query. A suggestion:

{
 ...
  "name": "Diaspora Project Site",
  "name_with_namespace": "Diaspora / Diaspora Project Site",
  "path": "diaspora-project-site",
  "path_with_namespace": "diaspora/diaspora-project-site",
  "issues_enabled": true,
  "compliance_frameworks": [ "sox" ], # this would be added in this issue
 ...
}

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references