coilyco-flight-deck/infrastructure
2
0
Fork 0
Code Issues 118 Pull requests Projects Releases Packages Wiki Activity Actions 2

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

New issue
Open
opened 2026-05-28 13:28:46 +00:00 by coilysiren · 0 comments
coilysiren commented 2026-05-28 13:28:46 +00:00
Owner
Copy link

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-06-17 08:40:14 +00:00
coilyco-ops added
P4
 and removed
P3
 labels 2026-07-10 09:00:23 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-515
issue-486
issue-529
issue-500
issue-483
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.