Add repository descriptors for the toolbox and martials.no pilots #55

Closed
opened 2026-11-21 21:10:29 +00:00 by martin · 1 comment
Owner

Summary

Add repository-owned Component descriptors for the Toolbox and martials.no pilots so their metadata comes from Forgejo repositories instead of only from the portal's central catalog data.

Context

The portal's catalog fixture currently models Personal/toolbox and Personal/martials.no as Components, but neither repository currently has a root catalog-info.yaml. The Forgejo provider therefore omits them.

Scope

  • Add a root catalog-info.yaml to each repository.
  • Preserve the existing stable entity names and accurate owner, lifecycle, system membership, repository/project annotation, and useful links; verify values against each repository rather than treating test fixtures as the source of truth.
  • Keep catalog tests independent of live Forgejo.

Acceptance criteria

  • Both repositories have a valid root Component descriptor on their default branch.
  • The descriptors preserve the stable Component refs and express verified ownership, lifecycle, system membership, Forgejo project identity, and relevant links.
  • The portal imports both Components without duplicate refs or unresolved relationships.
  • Existing fixture-based API and browser checks continue to pass without live Forgejo access.
## Summary Add repository-owned Component descriptors for the Toolbox and martials.no pilots so their metadata comes from Forgejo repositories instead of only from the portal's central catalog data. ## Context The portal's catalog fixture currently models Personal/toolbox and Personal/martials.no as Components, but neither repository currently has a root catalog-info.yaml. The Forgejo provider therefore omits them. ## Scope - Add a root catalog-info.yaml to each repository. - Preserve the existing stable entity names and accurate owner, lifecycle, system membership, repository/project annotation, and useful links; verify values against each repository rather than treating test fixtures as the source of truth. - Keep catalog tests independent of live Forgejo. ## Acceptance criteria - [ ] Both repositories have a valid root Component descriptor on their default branch. - [ ] The descriptors preserve the stable Component refs and express verified ownership, lifecycle, system membership, Forgejo project identity, and relevant links. - [ ] The portal imports both Components without duplicate refs or unresolved relationships. - [ ] Existing fixture-based API and browser checks continue to pass without live Forgejo access. ## Related - Personal/backstage#28 tracks the overall capability and depends on this pilot work.
Author
Owner

Superseded and split by target repository: Personal/toolbox#64 and Personal/martials.no#88. Continue in those issues; this combined Backstage issue is being closed to avoid duplicate tracking.

Superseded and split by target repository: [Personal/toolbox#64](https://code.martials.no/Personal/toolbox/issues/64) and [Personal/martials.no#88](https://code.martials.no/Personal/martials.no/issues/88). Continue in those issues; this combined Backstage issue is being closed to avoid duplicate tracking.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Personal/backstage#55
No description provided.