Skip to content

catalog-backend-module-annotate-scm-slug: Applicable kinds no longer configurable after migration #9397

Description

@Badbond

Workspace

catalog

📜 Description

While the constructor of AnnotateScmSlugEntityProcessor indicates that the kinds it applies to can be configured, the module does provide no means to pass such configuration nor to manually instantiate the processor.

👍 Expected behavior

I can configure which kinds AnnotateScmSlugEntityProcessor processes.

👎 Actual Behavior with Screenshots

The processor always only applies to Component kinds by default.

👟 Reproduction steps

Before migration in my own Backend module:

import { AnnotateScmSlugEntityProcessor } from '@backstage/plugin-catalog-backend';
        
// ...

        catalog.addProcessor(
          AnnotateScmSlugEntityProcessor.fromConfig(config, {
            kinds: ['API', 'Component', 'Resource', 'System'],
          }),
        );

After migration (no configuration options or other extension points):

// In packages/backend/src/index.ts
backend.add(
  import(
    '@backstage-community/plugin-catalog-backend-module-annotate-scm-slug'
  ),
);

📃 Provide the context for the Bug.

The AnnotateScmSlugEntityProcessor was moved from @backstage/plugin-catalog-backend to @backstage-community/catalog-backend-module-annotate-scm-slug since Backstage 1.49.0.

👀 Have you spent some time to check if this bug has been raised before?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

Are you willing to submit PR?

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions