change default namespace for all entities | Backstage | Page 1

winter yacht Apr 6, 2023, 6:11 PM

#

Hello,
How do i change the namespaces of all entities from default to the name of my github organization?

mellow sinew Apr 6, 2023, 10:24 PM

#

I don't think there's widespread adoption of namespacing as it seems to be the message that namespaces shouldn't be used currently -- though i'd love to see some more discussion on the topic of namespaces as it seems like a powerful feature.

winter yacht Apr 7, 2023, 8:20 AM

#

The problem I’m facing is that all the imported users and groups from github are mapped to User:default/* or Group:default/*. This prevents me from using the Templates feature along with assigning collaborators when creating a repo out of a template. Because during the register phase it tries to search for a group to assign the repo. The group in GitHub is having a combined slug of myOrg/myTeamName. But backstage tries default/myTeamName which doesnt exist in GitHub and i end up having a repo created with no one having access to it because the mapping didn’t happen.

I hope I’m not too cryptic..

winter yacht Apr 7, 2023, 11:24 AM

#

in the publish step i see this warning:

2023-04-06T20:38:14.588Z warn: Skipping admin access for myorg/group:default/mygroup, Not Found

shy egret Apr 10, 2023, 4:31 PM

#

you can use the GithubMultiOrgReaderProcessor to do this for org data specifically (even with a single org), it ingests org data with a configured namespace for the org https://github.com/backstage/backstage/blob/master/plugins/catalog-backend-module-github/src/processors/GithubMultiOrgReaderProcessor.ts

#

docs lacking but example usage here https://github.com/backstage/backstage/pull/5173

winter yacht Apr 11, 2023, 10:50 AM

#

thanks @shy egret this worked, however even when the new groups where under the correct org namespace. when creating a repo out of a template and use the new group myorg/mygroup..it still showed the warn in the github:publish step saying the group is not found and it's getting skipped.
this leads to a repo created without a team assigned to it as a collaborator

shy egret Apr 11, 2023, 3:00 PM

#

mm yeah, I suspect the problem is here
https://github.com/backstage/backstage/blob/f83c0446df80dd63dff180c8b776957eeab1c9a1/plugins/scaffolder-backend/src/scaffolder/actions/builtin/github/helpers.ts#L228
entityRefToName does name.replace(/^.*[:/]/g, ''); which transforms group:myorg/mygroup into just mygroup

#

maybe should be more like

name.replace(/^.*:/, '').replace('^default/', '');

or similar to remove the default namespace but not others?

winter yacht Apr 11, 2023, 5:14 PM

#

I am wondering if i can bypass this problem by using something like: myorg/{{( parameters.repoUrl | parseRepoUrl)['owner'] }} filter to get the team directly with the org attached to it and use it either in the collaborators field or the access field in the github:publish step?

winter yacht Apr 12, 2023, 6:21 AM

#

@shy egret do you think this makes sense?

#change default namespace for all entities