Skip to content

Static import Domains/Systems not appearing in production Backstage #2

@jonshaffer

Description

@jonshaffer

Problem

The catalog-info.yaml in this repo defines:

  • Group(hyperfluid)
  • Domain(hyperfluid)
  • Location(hyperfluid-github-locations) → points to hfs and hyperfluid-site repos

These entities are imported via static file locations in the Backstage app-config.yaml, but they are not appearing in the production catalog at backstage.hyperfluid.dev.

The same issue affects:

  • systmms/.githubDomain(systmms) missing
  • jonshaffer/.githubDomain(js) and System(personal) missing

Root cause (suspected)

The production config (app-config.tpl.yaml) does not include the catalog.locations section that references imports/index.yaml. Only the GitHub discovery providers are configured in production. Since .github repos are excluded from discovery (^(?!\.github$).* filter), these entities have no path into the production catalog.

Additional issue

The Location entity references hyperfluid-solutions/hyperfluid-site, but this repo does not exist. The actual repo is hyperfluid-solutions/hyperfluid.

Action needed

Pending a decision on the best approach for org-level entity definitions:

  1. Option A: Add catalog.locations to the production config template
  2. Option B: Remove the .github exclusion filter so discovery picks these up
  3. Option C: Move Domain/System definitions into the repos that are already discovered
  4. Option D: Define Domains/Systems as static YAML within the Backstage repo itself

Also fix the broken hyperfluid-sitehyperfluid repo reference regardless of approach chosen.

Context

Found during a Backstage catalog audit on 2026-04-19.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions