Remove the central personal-services System registration #53

Closed
opened 2026-11-21 21:10:29 +00:00 by martin · 3 comments
Owner

Summary

Remove the central catalog registration for the personal-services System after its canonical descriptor is discoverable from the cluster repository.

Context

The System currently lives in this repository's examples/systems.yaml, while Personal/cluster#86 adds the canonical System descriptor to the GitOps repository that owns the deployed workloads. Keeping both sources after discovery begins would create a duplicate System entity.

Scope

  • Wait for the descriptor in Personal/cluster#86 to be merged.
  • Remove the default local registration of examples/systems.yaml and retire the central System file.
  • Preserve the controlled E2E System fixture and ensure it remains independent of live Forgejo.
  • Verify the discovered System and existing Components' system relationships.

Acceptance criteria

  • Personal/cluster#86 is merged with the stable system:default/personal-services descriptor.
  • The local app no longer loads a central copy of the System, while the E2E fixture still provides its controlled copy.
  • Backstage discovers exactly one personal-services System and the pilot Components resolve their spec.system relationships.
  • Relevant backend and fixture-based E2E checks pass without requiring a Forgejo token.

Dependencies

## Summary Remove the central catalog registration for the personal-services System after its canonical descriptor is discoverable from the cluster repository. ## Context The System currently lives in this repository's `examples/systems.yaml`, while Personal/cluster#86 adds the canonical System descriptor to the GitOps repository that owns the deployed workloads. Keeping both sources after discovery begins would create a duplicate System entity. ## Scope - Wait for the descriptor in Personal/cluster#86 to be merged. - Remove the default local registration of `examples/systems.yaml` and retire the central System file. - Preserve the controlled E2E System fixture and ensure it remains independent of live Forgejo. - Verify the discovered System and existing Components' system relationships. ## Acceptance criteria - [x] Personal/cluster#86 is merged with the stable `system:default/personal-services` descriptor. - [x] The local app no longer loads a central copy of the System, while the E2E fixture still provides its controlled copy. - [x] Backstage discovers exactly one `personal-services` System and the pilot Components resolve their `spec.system` relationships. - [x] Relevant backend and fixture-based E2E checks pass without requiring a Forgejo token. ## Dependencies - Personal/cluster#86 — Add the personal-services System to the cluster catalog descriptor. ## Related - Personal/backstage#28 tracks the overall repository-owned catalog work.
martin changed title from Move the personal-services System into its owning repository descriptor to Remove the central personal-services System registration 2026-11-21 22:01:09 +00:00
Author
Owner

Progress

  • Identified Personal/cluster as the canonical owner of personal-services: its GitOps configuration manages the cluster workloads represented by this System. The descriptor is tracked in Personal/cluster#86, with PR #87 open.
  • This issue now covers removing the central examples/systems.yaml source after #86 merges and verifying that components still resolve the System.
## Progress - Identified `Personal/cluster` as the canonical owner of `personal-services`: its GitOps configuration manages the cluster workloads represented by this System. The descriptor is tracked in [Personal/cluster#86](https://code.martials.no/Personal/cluster/issues/86), with [PR #87](https://code.martials.no/Personal/cluster/pulls/87) open. - This issue now covers removing the central `examples/systems.yaml` source after #86 merges and verifying that components still resolve the System.
Author
Owner

Progress

  • The canonical System owner is Personal/cluster; its descriptor is in cluster PR #87.
  • Opened Backstage PR #57 to remove the central System source. It is explicitly gated on #87 merging first, then requires post-merge live catalog verification.
## Progress - The canonical System owner is `Personal/cluster`; its descriptor is in [cluster PR #87](https://code.martials.no/Personal/cluster/pulls/87). - Opened [Backstage PR #57](https://code.martials.no/Personal/backstage/pulls/57) to remove the central System source. It is explicitly gated on #87 merging first, then requires post-merge live catalog verification.
Author
Owner

Progress

  • Personal/cluster#86 is complete; its System descriptor is on main via cluster PR #87.
  • Backstage PR #57 removes the central duplicate. Live catalog verification against that branch after #87 merged confirmed one System and resolved component memberships.
  • This issue remains open until PR #57 is merged and the behavior is verified on main.
## Progress - Personal/cluster#86 is complete; its System descriptor is on `main` via [cluster PR #87](https://code.martials.no/Personal/cluster/pulls/87). - [Backstage PR #57](https://code.martials.no/Personal/backstage/pulls/57) removes the central duplicate. Live catalog verification against that branch after #87 merged confirmed one System and resolved component memberships. - This issue remains open until PR #57 is merged and the behavior is verified on `main`.
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#53
No description provided.