Allow mapping and dependencies of Kinds other than Components

[aladjadj]

Is your feature request related to a problem? Please describe.

Currently, the plugin only manages the Component kind and excludes managing Resources (Database, Redis, etc) or more high-level views like System or Domain as Business Service.

Also, we want to use Backstage as the source of thrust to pilote PagerDuty with fine granularity without manual actions.
In an organization with Platform, teams managed infrastructure resources it could be interesting to map each resource to the component to see affected.

I don't see any decision about this current limitation, do you have resources about that ?

Describe the solution you'd like

Assumption schema

graph TD;
    service1-->service2;
    service2-->business_service;
    database_service1-->service1;
    database_service2-->service2;
    db_instance_shared_like_rds-->database_service1;
    db_instance_shared_like_rds-->database_service2;

Loading

pg_instance_shared: Resource could be impacted by an performance issue and trigger Platform OnCall
database_*: Resource could be impacted by a performance issue without impact pg_instance_shared and trigger Engineer or Platform OnCall
service_*: The component could see the impact on the dedicated database.

Final the goal is to allow mapping of Resources (kind) to PagerDuty + Dependencies

Don't hesitate if you have any extra questions.