sean/binjovi-plans
Watch
1
0
Fork
You've already forked binjovi-plans
 0
Code Issues Pull requests 1 Projects Releases 156 Packages Wiki Activity

chore: retire zot-src, argo-workflows and pipelines from the catalog #136

Merged
binjovi-bot merged 3 commits from sean/retire-argo-bundle into trunk 2026-09-08 21:37:17 +00:00 AGit
Conversation 0 Commits 3 Files changed 7 +48 -226
sean commented 2026-09-08 21:36:26 +00:00
Owner
Copy link

Three commits. zot-src was the last project in the fleet naming argo_workflow: a shadow project that never created a single Workflow object, while the image that runs registry.sean.farm is built by the Flux-managed Shipwright Build/zot from the same repository. The old guard asserted the entry was PRESENT; it is replaced with the opposite assertion in its own pass with three negative controls, and the deployment-target clause filters to objects because binjovi and bytey carry plain strings there and jq otherwise aborts. argo-workflows goes because the engine it deployed is gone. pipelines goes because all five ArgoCD Applications and all four image Deployments it named are NotFound. The catalog is now 29 projects with ZERO naming argo_workflow. https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76

Three commits. zot-src was the last project in the fleet naming argo_workflow: a shadow project that never created a single Workflow object, while the image that runs registry.sean.farm is built by the Flux-managed Shipwright Build/zot from the same repository. The old guard asserted the entry was PRESENT; it is replaced with the opposite assertion in its own pass with three negative controls, and the deployment-target clause filters to objects because binjovi and bytey carry plain strings there and jq otherwise aborts. argo-workflows goes because the engine it deployed is gone. pipelines goes because all five ArgoCD Applications and all four image Deployments it named are NotFound. The catalog is now 29 projects with ZERO naming argo_workflow. https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
zot-src was the last project in the fleet naming `argo_workflow`. It never
created a single Workflow object: `control_mode: shadow` is rejected outright
by `project_authority.ex`, so the entry built nothing. The image that actually
runs `registry.sean.farm` is built by the Flux-managed Shipwright `Build/zot`
in namespace `shipwright-build`, which clones the same `sean/zot-src`
repository. Deleting the entry changes nothing about the registry and takes the
fleet to zero projects naming the executor.

The old guard asserted the entry was PRESENT. Replace it with the opposite
assertion, in its own pass so a mutated copy can be run through it, and give it
three negative controls: a build executor, a release executor and a deployment
target that names `argo_workflow` must each turn it red on its own.

The deployment-target clause filters to objects. `binjovi` and `bytey` carry
plain strings there, and without the filter jq aborts with "Cannot index string
with string" and the guard never runs at all.

The Forgejo mirror `sean/zot-src` and
`kubernetes/flux/infrastructure/gitmirrors/zot-src.yaml` stay. The Shipwright
Build clones from them.

Claude-Session: https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
The `argo-workflows` gitops-argocd project keeps ArgoCD Application
`argo-workflows` synced from `sean/argo-workflows`. The Argo Workflows engine
is being removed, so the project goes first: Binjovi must stop managing the
Application before the Application is deleted, or the next deploy of this
project syncs a target that is not there.

Nothing else in the fleet references it. The Application is already an orphan
in ArgoCD terms -- its tracking-id names `pipelines-argocd`, an app-of-apps
that was deleted with Pipelines -- so this bundle entry was the only thing
still tending it.

`scripts/check` drops it from the list of projects required to be
native-on-argocd. The other nine stay: ArgoCD itself is not being retired.

The Application and the objects it left in namespace `workflows` are deleted
by a tombstone Job in `sean/seanfarm`, in the release after this one.

Claude-Session: https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
chore: retire the archived pipelines project
All checks were successful
binjovi/ci Binjovi completed the frozen plan
Details
62b76c22db
 
`sean/pipelines` is archived. Its entry here deployed five ArgoCD Applications
-- pipeline-base, pipelines, pipelines-operator, pipelines-project-registry,
workflows-infra-bare -- and image-deployed four Deployments. Every one of the
nine is NotFound in the live cluster, and namespace `pipelines-operator-system`
does not exist, so the entry named nothing: a release of this project would
have failed at its first deploy step and its availability check points at a
Service that is gone.

`tests/native-catalog-test` carried a 15-line contract pinning those exact
five Applications and four image deployments. Replace it with the opposite
assertion -- no project named `pipelines` -- so a re-added entry is caught
instead of a changed one. Verified by re-adding an entry: the check goes red.

The recipe goes with it. Nothing builds this image any more.

Claude-Session: https://claude.ai/code/session_01KZoQin34jeyt6nDGqvJA76
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
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
sean/binjovi-plans!136
No description provided.