🐛 azure-devops: Error while using EntityAzurePipelinesContent outside Entity page

[c4rth]

Workspace

azure-devops

📜 Description

I'm trying to use the EntityAzurePipelinesContent in a custom component.
An error is thrown (see screenshots):
Cannot route to routeRef{type=absolute,id=azure-pipelines-entity-content} with parent routeRef{type=absolute,id=catalog:entity} as it has parameters

👍 Expected behavior

Show the Azure DevOps pipelines list.

👎 Actual Behavior with Screenshots

console:

👟 Reproduction steps

Custom component using EntityAzurePipelinesContent:

<EntityProvider entity={serviceEntity}>
  <TabbedLayout>
    {isAzureDevOpsAvailable(serviceEntity) || isAzurePipelinesAvailable(serviceEntity) ?
      <TabbedLayout.Route path="/ci-cd" title="CI/CD">
        <EntityAzurePipelinesContent />
      </TabbedLayout.Route>
      : null
    }
  </TabbedLayout>
</EntityProvider>

📃 Provide the context for the Bug.

If I add a new component in the azure-devops plugin (with createComponentExtension) using the same EntityPageAzurePipelines component, and using it in my component, it works.

export const EntityAzurePipelinesCard = azureDevOpsPlugin.provide(
  createComponentExtension({
    name: 'EntityAzurePipelinesCard',
    component: {
      lazy: () => import('./components/EntityPageAzurePipelines').then(m => m.EntityPageAzurePipelines),
    },
  }),
);

Moreover if I use this EntityAzurePipelinesCard in the EntityPage, it also works.

👀 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?

• I have read the Code of Conduct

Are you willing to submit PR?

No, but I'm happy to collaborate on a PR with someone else

[awanlin]

Hi @c4rth, this isn't an intended use case. What's you end goal? Why are you wanting to use it this way?

[c4rth]

Hi @awanlin
As Backstage doesn't manage versioning of components (services, API, ...), I created components to manage it for my specific use case (adding custom annotations, frontend and backend plugin, ...).
The custom components are for system, API and service.
For a versioned service, I would like to show Azure DevOps pipelines related to a versioned service that is a standard entity but shown in my custom component, so not using the default Entity page .
Here are some screenshots:

So my goal was to reuse the azure-devops plugin to show the Azure Devops Pipelines, and potentially the other Azure DevOps items (like PR), without 'hacking' them in a copy of the frontend plugin.