Task Description (Required)

As part of our investigation into how to import model and model servers from multiple sources (e.g. Kubeflow, RHOAI MR, Quay, etc), we need to look at ways to import entities into the RHDH catalog, without relying upon a Git repository.

We have prototype some vanilla HTTP servers which, when their host names are added to Backstage's allowed hosts  configuration, but there are some minor hiccups because it is not a full on github server.

Backstage provides two non-git options for ingesting entities into the catalog:
1) Custom Entity Providers

2) Custom Processors

This issue will focus on the latter (Custom Processors)

While Custom Entity Providers appear to be the recommended solution for ingesting catalog entities from external sources:

There are two main options for how to ingest data into the catalog: making a custom entity provider, or making a custom processor. They both have strengths and drawbacks, but the former would usually be preferred. Both options are presented in a dedicated subsection below.

There does appear to be strengths and drawbacks for each approach, so we will need to consider which ones fit our problem (importing models/model servers into the catalog). Unlike RHDHPAI-505, there doesn't appear to be any pre-existing RHDH plugins that make use of custom processors, so we may need to find external backstage plugins to use as reference, or rely solely on the Backstage documentation.

Tasks:

1. Stand up a basic Backstage plugin in RHDH, from which a custom entity provider could be written
2. Investigate how Custom Processors work, and how they might be used to import 
3. Document any drawbacks to this approach 
4. If possible, provide a basic proof of concept using custom processors