Skip to content

Return all linked projects/namespaces when fetching policies

What does this MR do and why?

This MR changes how project/namespaces are fetched in the service responsible for fetching policies based on policy scopes. Currently it was scoped to single root group, however as we see for self-managed customers, policies are used across multiple root groups.

From security perspective, we are using this service only in GraphQL API, where Groups/Projects are additionally authorized before returned to API user.

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.

How to set up and validate locally

  1. Create 2 root groups with 1 subgroup in each
  2. Create policy in one root group, link same SPP to the second group.
  3. Modify the policy to have group scope to both subgroups
  4. Merge changes
  5. Go to Policies list for both root groups, you should see the policy with correct information about scoped subgroups

Numbered steps to set up and validate the change are strongly suggested.

Related to #468384 (closed)

Edited by Alan (Maciej) Paruszewski

Merge request reports

Loading