Skip to content
Snippets Groups Projects

Inherit permissions from parent group

Merged username-removed-444 requested to merge dz-nested-group-access into master
All threads resolved!

What does this MR do?

Includes group parents into group access policy

Are there points in the code the reviewer needs to double check?

no

Why was this MR needed?

It allows access to nested group if you have membership in one of it parents

Screenshots (if relevant)

no

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ce/issues/2772

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • This seems too simple! Maybe it is all we need - I'd love it if that was the case. I have some questions:

    1. Does Users::RefreshAuthorizedProjectsService handle this properly?
    2. What about project group links?
    3. How do we find out which groups you have access to?
  • This seems too simple!

    @smcgivern I don't like huge merge requests so prefer to implement isolated parts. This one is focused on group access policy. More is coming.

  • added 1 commit

    • 9f39953e - Improve Group#users_with_parents method

    Compare with previous version

  • username-removed-444 resolved all discussions

    resolved all discussions

  • Does Users::RefreshAuthorizedProjectsService handle this properly?

    @smcgivern I will make tests to see how it handles nested groups in separate MR

    What about project group links?

    separate MR

    How do we find out which groups you have access to?

    by collection your membership from nested group up to parent group. If you are member of any - you have access.

    Edited by username-removed-444
  • username-removed-444 enabled an automatic merge when the pipeline for 9f39953e succeeds

    enabled an automatic merge when the pipeline for 9f39953e succeeds

  • username-removed-444 mentioned in merge request !8308 (merged)

    mentioned in merge request !8308 (merged)

  • mentioned in commit c595b418

  • by collection your membership from nested group up to parent group. If you are member of any - you have access.

    With this question I meant: how can I enumerate all the groups someone has access to?

  • @smcgivern you get groups via membership. Then get the rest from routes table (everything that has authorized groups paths as prefix)

  • Please register or sign in to reply
    Loading