Add Backstage catalog descriptors for the service and API #61
Labels
No labels
automerge
bug
dependencies
duplicate
help wanted
invalid
lang
rust
migrations
opencode
question
security
type
documentation
type
enhancement
type
maintenance
type
refactor
vulnerability
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Reference
Personal/recurring-events#61
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Make the recurring-events service and its API discoverable from repository-owned catalog metadata.
Context
The repository owns the root openapi.yaml contract, but has no root catalog-info.yaml. The Backstage portal currently represents the Component recurring-events and API recurring-events-api in its central example catalog.
Scope
Acceptance criteria
Related
Progress
openapi.yaml.$textagainst the local OpenAPI file; refs are unique andgit diff --checkpassed. End-to-end catalog ingestion remains to be verified in Personal/backstage#28. The PR is open and not merged.Progress
9fcbb2a8eeeeb6d49c727dd6a73256e8fcffb472; the root descriptor now defines the Component and API onmain.$textagainst the repository's OpenAPI file; entity refs are unique andgit diff --checkpassed. End-to-end catalog ingestion and API rendering remain to be verified under Personal/backstage#28.Progress
recurring-events-apiexample registration was removed by merged Personal/backstage#56 (86487c2fe5e2318710f0d16a7665e0b1cbb64a10), so the repository descriptor is now the catalog source for that API.better-sqlite3Node ABI mismatch. This issue remains open until that behavior is verified.Completed by merged PR #62 (
9fcbb2a8eeeeb6d49c727dd6a73256e8fcffb472). In an isolated Backstage run against the live public Forgejo descriptors, the Component and API imported once, the API definition resolved fromopenapi.yaml, the Component/API and System relations resolved, and owner/lifecycle/project annotations and repository/service links matched expectations. The controlled fixture E2E suite also passed all 5 tests.