🐛 Bug Report: Github Org Data does not have option to import github team under default namespace about backstage

[vinzscam]

Thank you for reporting this. We are working on a fix in #24700

In the meantime I can give you a workaround to apply in your packages/backend/src/index.ts

+ import {
+   coreServices,
+   createBackendModule,
+ } from '@backstage/backend-plugin-api';
+ import { catalogProcessingExtensionPoint } from '@backstage/plugin-catalog-node/alpha';
+ import { GithubOrgEntityProvider } from '@backstage/plugin-catalog-backend-module-github';

...

- backend.add(import('@backstage/plugin-catalog-backend-module-github-org'));
+ backend.add(
+   createBackendModule({
+     pluginId: 'catalog',
+     moduleId: 'example-custom-processor',
+     register(env) {
+       env.registerInit({
+         deps: {
+           catalog: catalogProcessingExtensionPoint,
+           config: coreServices.rootConfig,
+           logger: coreServices.logger,
+         },
+         async init({ catalog, config, logger }) {
+           catalog.addEntityProvider(
+             GithubOrgEntityProvider.fromConfig(config, {
+               // same options as before
+             }),
+           );
+         },
+       });
+     },
+   }),
+ );

Let me know if this works!

[prasoon-pxc]

@vinzscam --> Thanks for your reply, I have upgraded my backstage version to 1.27.0 and right now groups are ingesting under default namespace.
and sorry I have not got the time to test your above code on old version.
Again Thanks

[vinzscam]

@vinzscam --> Thanks for your reply, I have upgraded my backstage version to 1.27.0 and right now groups are ingesting under default namespace. and sorry I have not got the time to test your above code on old version. Again Thanks

ah no problem, glad everything is working as expected 🙏