Support namespacing groups ingested via the GithubOrgReaderProcessor

Feature Suggestion

The current functionality for importing GitHub org data allows for targeting a specific GitHub org and ingesting all users/team as Users/Groups under the default namespace.

Under our use-case, we have a GHE instance that supports having multiple GitHub orgs (usually created per dept. or domain). If we import multiple orgs that contain the same team names then they will both merge under the same Group in the default namespace (I assume, haven’t tested). It would be helpful if we could namespace the imported Group that indicates the GitHub org they reference

For example, I have the following GitHub orgs and teams: FooOrg: team-abc, team-efg BarOrg: team-abc, team-xyz

After importing from both orgs, I would expect the following entities: Group:FooOrg/team-abc, Group:FooOrg/team-efg, Group:BarOrg/team-abc, Group:BarOrg/team-xyz

This would allow components to specify their owner fields to correctly reflect team ownership.

Another thing I would like to note is that users in our GHE may have multi-org memberships so in our use-case it wouldn’t make sense to namespace Users since there will only be one unique set of usernames.

Possible Implementation

Context

There might be related to discussions in https://github.com/backstage/backstage/issues/4089 and I’m not sure how exactly this would fit in with the proposal described there.

[andrewthauer]

#4977 is relevant to this as well.

[benjdlambert]

PR is in progress, @kuangp just hasn’t had time to fix up the work yet. Removing the stale label 😃