You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
API kinds are unable to relate back to components in graph view. Is there a way of linking a kind API back to a component without creating a custom processor that emit the relations.
When using a spec relationship link such as apiProvidedBy be able to link back to a component and it show up in the relations gragh.
👎 Actual Behavior with Screenshots
Currently it looks like their is no way to link back a API to a component
👟 Reproduction steps
apiVersion: backstage.io/v1alpha1kind: Componentmetadata:
name: test-apititle: test.apiannotations:
namespace: defaultdescription: This is a test apispec:
owner: guesttype: servicelifecycle: experimental
---
apiVersion: backstage.io/v1alpha1kind: APImetadata:
name: Test.API.v1_1title: Test.API.v1_1namespace: defualtdescription: >- Test Apispec:
type: openapilifecycle: experimentalowner: guestapiProvidedBy: Component:bunnings-technology-delivery/test-api # Way to link back to component, currently using apiProvidedBy does not work definition:
$text: swagger.json
📃 Provide the context for the Bug.
Use case
We are using a custom entity provider to inject our APIs directly into backstage from their swagger mapping files. Though are keeping the component as a catalog-info file in each repo. We don't want to have to update the catalog info file every time there is a change to our APIs and instead just edit the custom entity provider to link back to our component.
Yeah, unfortunately this isn't part of model right now, so those relations won't be emitted correctly.
You can however follow the guidance in the other issue, and create your own processor which would emit the correct relation by using the spec.apiProvidedBy field in the entities if it exists.
📜 Description
API kinds are unable to relate back to components in graph view. Is there a way of linking a kind API back to a component without creating a custom processor that emit the relations.
Was mentioned being an issue under #13535
👍 Expected behavior
When using a spec relationship link such as
apiProvidedBy
be able to link back to a component and it show up in the relations gragh.👎 Actual Behavior with Screenshots
Currently it looks like their is no way to link back a API to a component
👟 Reproduction steps
📃 Provide the context for the Bug.
Use case
We are using a custom entity provider to inject our APIs directly into backstage from their swagger mapping files. Though are keeping the component as a
catalog-info
file in each repo. We don't want to have to update the catalog info file every time there is a change to our APIs and instead just edit the custom entity provider to link back to our component.🖥️ 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: