Make Forgejo discovery resilient and continuously refreshed #24

Closed
opened 2026-11-07 21:51:25 +00:00 by martin · 1 comment
Owner

Goal

Replace startup-only discovery with an explicit refresh lifecycle. Evaluate a scheduled backend entity provider against the current generated-file script and document the selected architecture.

Acceptance criteria

  • Refresh works without restarting the portal.
  • Pagination, public/authenticated access, API failures, and request timeouts are tested.
  • Failed refreshes preserve the last successful catalog; successful refreshes reconcile removed repositories.
  • Entity naming is deterministic, with collision handling and stable references.
  • Public-only and authenticated modes, owner selection, and freshness/error reporting are documented.
  • Coordinate descriptor precedence with the repository-owned metadata issue.

Depends on

#23

Phase

2 — Useful developer workflows

## Goal Replace startup-only discovery with an explicit refresh lifecycle. Evaluate a scheduled backend entity provider against the current generated-file script and document the selected architecture. ## Acceptance criteria - [x] Refresh works without restarting the portal. - [x] Pagination, public/authenticated access, API failures, and request timeouts are tested. - [x] Failed refreshes preserve the last successful catalog; successful refreshes reconcile removed repositories. - [x] Entity naming is deterministic, with collision handling and stable references. - [x] Public-only and authenticated modes, owner selection, and freshness/error reporting are documented. - [x] Coordinate descriptor precedence with the repository-owned metadata issue. ## Depends on #23 ## Phase 2 — Useful developer workflows
Author
Owner

Progress

PR #51 was merged to main as f4cbb1d; follow-up PR #52 was merged as 1393edc on 2026-11-21. The scheduled provider imports only repository descriptors, parses them, canonicalizes kind:namespace/name refs, and rejects invalid identities or collisions before applying a full snapshot. A rejected refresh preserves the last successful catalog; names are never rewritten.

The design and collision policy are documented in docs/forgejo-discovery.md and docs/decisions/001-forgejo-catalog-source-of-truth.md.

Validation

Woodpecker PR pipeline #140 passed all steps, including E2E. Local validation passed: frozen install, typecheck, lint, formatting, backend build, and 12 tests across the full unit suite. All acceptance criteria are complete.

## Progress PR #51 was merged to `main` as `f4cbb1d`; follow-up PR #52 was merged as `1393edc` on 2026-11-21. The scheduled provider imports only repository descriptors, parses them, canonicalizes `kind:namespace/name` refs, and rejects invalid identities or collisions before applying a full snapshot. A rejected refresh preserves the last successful catalog; names are never rewritten. The design and collision policy are documented in [`docs/forgejo-discovery.md`](https://code.martials.no/Personal/backstage/src/branch/main/docs/forgejo-discovery.md) and [`docs/decisions/001-forgejo-catalog-source-of-truth.md`](https://code.martials.no/Personal/backstage/src/branch/main/docs/decisions/001-forgejo-catalog-source-of-truth.md). ## Validation Woodpecker PR pipeline #140 passed all steps, including E2E. Local validation passed: frozen install, typecheck, lint, formatting, backend build, and 12 tests across the full unit suite. All acceptance criteria are complete.
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.

Reference
Personal/backstage#24
No description provided.