-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Bug Report: Github Org Data does not have option to import github team under default namespace #24684
Comments
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 + 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! |
@vinzscam --> Thanks for your reply, I have upgraded my backstage version to |
ah no problem, glad everything is working as expected 🙏 |
📜 Description
I had already setup existing backstage with old backend system and I was using Github org data to ingest user&teams into Bakctage, it was working fine and user&teams are ingesting under
default
namespace, and after that when I need to reference owner field incatalog-info.yaml
file I just have to mention the team name without using full reference of namespace.In New Backend System, Now github teams are ingesting under namespace which is name of your github org.
👍 Expected behavior
I want to have an option where I can ingest github teams under default namespace or make my org as a default namespace so that I do not need to change all my
catalog-info.yaml
file to include full reference of namespaces inowner
field.👎 Actual Behavior with Screenshots
👟 Reproduction steps
Use Github org data to ingest Github user and teams into backstage and then reference one team in
catalog.info.yaml
file under owner field:📃 Provide the context for the Bug.
No response
🖥️ Your Environment
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
None
The text was updated successfully, but these errors were encountered: