Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10548

sort out AI related filtering for Backstage API objects

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Undefined Undefined
    • None
    • None
    • model-registry-bridge

      Unlike with Components and Resources, our Backstage Catalog API does not specify as unique `spec.type` setting for API objects, since Backstage is already opinionated on that field's setting for API objects.

      Hence, as we are filtering for "AI content" with our `bac get component` and `bac get resource` calls based on the `spec.type` settings for those, we need to devise an alternative for API objects.

      Options include

      • setting a precise tag or label during our `bac new-model` processing that the queries can leverage
      • query all the API objects, and then check the `spec.dependencyOf` field and if they point to an AI Component, then include that API instance in what is returned.
      • Or if the person who takes this on thinks of something even better, go for it

              Unassigned Unassigned
              gmontero@redhat.com Gabe Montero
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: