Remove superseded deploy/repo-recall.yml after repo-recall#97 migration #174

Open
opened 2026-05-28 13:28:46 +00:00 by coilysiren · 0 comments
Owner

Remove the superseded deploy/repo-recall.yml

coilysiren/repo-recall#97 migrated repo-recall's deploy off GitHub Actions to
the in-cluster Forgejo runner + registry, and moved the canonical deploy
manifest into the repo-recall repo at deploy/repo-recall.yml (matching the
pattern backend established in coilysiren/backend#25, which removed its
infrastructure copy).

infrastructure/deploy/repo-recall.yml is now a stale duplicate. It still
references the GHCR api image and lacks the deployer ServiceAccount.

Work

  • Delete infrastructure/deploy/repo-recall.yml.
  • Delete infrastructure/docs/repo-recall-deploy.md (or rewrite it to point at
    the in-repo manifest + Forgejo pipeline). It currently documents the dead
    GHCR + pull-side systemd path.
  • Confirm nothing else in infrastructure applies that path.

Source of truth is now coilysiren/repo-recall:deploy/repo-recall.yml.

## Remove the superseded `deploy/repo-recall.yml` coilysiren/repo-recall#97 migrated repo-recall's deploy off GitHub Actions to the in-cluster Forgejo runner + registry, and moved the canonical deploy manifest **into** the repo-recall repo at `deploy/repo-recall.yml` (matching the pattern backend established in coilysiren/backend#25, which removed its infrastructure copy). `infrastructure/deploy/repo-recall.yml` is now a stale duplicate. It still references the GHCR api image and lacks the deployer ServiceAccount. ### Work - Delete `infrastructure/deploy/repo-recall.yml`. - Delete `infrastructure/docs/repo-recall-deploy.md` (or rewrite it to point at the in-repo manifest + Forgejo pipeline). It currently documents the dead GHCR + pull-side systemd path. - Confirm nothing else in infrastructure applies that path. Source of truth is now `coilysiren/repo-recall:deploy/repo-recall.yml`.
coilysiren added
P3
and removed
P2
labels 2026-05-31 07:00:33 +00:00
Sign in to join this conversation.
No labels
P0
P1
P2
P3
P4
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
coilyco-flight-deck/infrastructure#174
No description provided.