paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 4 Packages Projects Releases Wiki Activity

Merge pull request #24936 from hghtwr/master

Browse Source 
#24889 - Feature: Fetch Gitlab users for self-hosted Gitlab based on group assignment
This commit is contained in:
Ben Lambert
2024-06-25 10:52:37 +02:00
committed by GitHub
parent 352438ba58 206698c311
commit 9de9d0820b
13 changed files with 726 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/integrations/gitlab/org.md
+14 -1
View File
@@ -196,11 +196,24 @@ which contain members will be ingested.
### Users
For self hosted, all `User` entities are ingested from the entire instance.
For self hosted, all `User` entities are ingested from the entire instance by default.
For gitlab.com `User` entities for users who have [direct or inherited membership](https://docs.gitlab.com/ee/user/project/members/index.html#membership-types)
of the top-level group for the configured group path will be ingested.
In both cases (SaaS & self hosted), you can limit the ingested users to users directly assigned to the group defined in your `app-config.yaml` by setting the configuration key `restrictUsersToGroup: true`. This is especially useful when you have a large user base that you don't want to import by default.
```yaml
catalog:
providers:
gitlab:
yourProviderId:
host: gitlab.com ## Could also be self hosted.
orgEnabled: true
group: org/teams # Required for gitlab.com when `orgEnabled: true`. Optional for self managed. Must not end with slash. Accepts only groups under the provided path (which will be stripped)
restrictUsersToGroup: true # Backstage will ingest only users directly assigned to org/teams.
```
### Limiting `User` and `Group` entity ingestion in the provider
Optionally, you can limit the entity types ingested by the provider when using