coulomb/prj-state-hub-retirement
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Correct T07: reuse-surface is live and stale; state-hub was mostly a false alarm

Browse source 
Checking each image reference's liveness separated the two cases the first pass
treated alike.

reuse-surface is a live Deployment on gitea, pinned to a 2026-07-07 commit and 22
commits behind main. Its CI moved to forgejo at 21:25 that same day, three hours
after the pinned commit, and has published :latest and :main-<short> there ever
since. Producer migrated, consumer did not.

state-hub's Deployment is already on forgejo with the current tag scheme. Its
only gitea reference is a completed one-shot alembic-init Job that does not
re-run on its own, so "unable to run its schema migration" was wrong. Residual
risk is a chart template recreating it.

No repository rename occurred — this is a registry migration in which one
consumer was left behind.

An image reference is not a dependency until something can act on it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-08-20 08:54:21 +02:00
parent d9867bd783
commit 23631f0239
3 changed files with 43 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

20
workplans/SHR-WP-0002-predecessor-and-deployment-reality.md
View file

@ -238,6 +238,7 @@ decision route rather than adding it unilaterally.
id: SHR-WP-0002-T07
status: todo
priority: high
state_hub_task_id: "07636ddf-a26b-4760-8353-2532af9fd938"
```
**The registry dependency, found 2026-08-20 and not previously tracked.**
@ -249,8 +250,23 @@ is the complete set).
Nothing breaks on decommission day, because running pods already hold their
images. It breaks at the next restart, reschedule or scale-up, as
`ImagePullBackOff`. One of the two is **State Hub's own migration job** — this
project's subject, unable to run its schema migration.
`ImagePullBackOff`.
**The two are not equally urgent** (corrected 2026-08-20 after checking each
reference's liveness):
- **`reuse-surface` — live and stale.** A running Deployment on the old
registry, pinned to a 2026-07-07 commit and **22 commits behind** main. Its CI
switched to forgejo three hours after that commit and has published there ever
since; the deployment was never repointed. **This is the one that must move
before 2026-08-31.**
- **`state-hub` — mostly a false alarm.** The Deployment is already on
`forgejo.coulomb.social/coulomb/state-hub:main-d8808bf`. The gitea reference is
a *completed* one-shot Job that will not re-run by itself; the residual risk is
a chart template recreating it. Worth cleaning, not urgent.
There was **no repository rename**. This is a registry migration (gitea →
forgejo, early July) in which producers moved and one consumer did not.
`forgejo.coulomb.social` is already on railiance01, so the work is retag, push,
update manifest. Routed to `railiance-platform`; ownership of the `reuse-surface`