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/.github → Domain(systmms) missing
jonshaffer/.github → Domain(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:
- Option A: Add
catalog.locations to the production config template
- Option B: Remove the
.github exclusion filter so discovery picks these up
- Option C: Move Domain/System definitions into the repos that are already discovered
- Option D: Define Domains/Systems as static YAML within the Backstage repo itself
Also fix the broken hyperfluid-site → hyperfluid repo reference regardless of approach chosen.
Context
Found during a Backstage catalog audit on 2026-04-19.
Problem
The
catalog-info.yamlin this repo defines:Group(hyperfluid)Domain(hyperfluid)Location(hyperfluid-github-locations)→ points tohfsandhyperfluid-sitereposThese 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/.github→Domain(systmms)missingjonshaffer/.github→Domain(js)andSystem(personal)missingRoot cause (suspected)
The production config (
app-config.tpl.yaml) does not include thecatalog.locationssection that referencesimports/index.yaml. Only the GitHub discovery providers are configured in production. Since.githubrepos 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 ishyperfluid-solutions/hyperfluid.Action needed
Pending a decision on the best approach for org-level entity definitions:
catalog.locationsto the production config template.githubexclusion filter so discovery picks these upAlso fix the broken
hyperfluid-site→hyperfluidrepo reference regardless of approach chosen.Context
Found during a Backstage catalog audit on 2026-04-19.