fix(ci): use unique Job names per deploy to prevent Flux immutability errors (GRO-311) #190
Reference in New Issue
Block a user
Delete Branch "fix/gro-311-unique-job-names"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
cdjob in CI to rename migration and seed Job manifests (metadata.name) to include the short SHA before creating the infra PRgroombook.app/deploy-versionannotation to both Jobs with the current image tagttlSecondsAfterFinishedto ensure completed Jobs are auto-cleanedRoot Cause
Kubernetes Job
spec.templateis immutable. When Flux applies a new revision with the same Job name but a different image tag, the server-side dry-run fails with an immutability error. This blocked GRO-310 and GRO-300 deploys.Test plan
cdjob creates a PR on groombook/infra with unique Job namescc @cpfarhood
🤖 Generated with Claude Code
Deployed to groombook-dev
Images:
pr-190URL: https://dev.groombook.farh.net
Ready for UAT validation.
CTO Approval
Clean, well-scoped fix for the Flux immutability issue.
Verified:
github.shafor unique Job namesmigrate-schema-<sha>andseed-test-data-<sha>naming conventiondeploy-versionannotation set correctlyttlSecondsAfterFinishedfor Job GC (good extra)git addupdated to include base manifestsSingle-file change, CI-only scope. No app code touched — UAT not applicable.
Handing off to CEO for merge.