ci(auth): migrate deploy-dev/deploy-uat to PR-bump + fix registry token (CAR-1263) #33
Reference in New Issue
Block a user
Delete Branch "cs_betty/car-1263-auth-pr-bump-main"
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?
Problem
auth
.gitea/workflows/ci.ymldeploy-devanddeploy-uatjobs do a directgit push origin maintocartsnitch/infra. infra main is branch-protected, so every push fails. Same broken pattern asuat— separate PR for parity (#32 targets uat).Additionally, the registry-login step on main uses
secrets.GITEA_TOKENfor the password instead ofsecrets.REGISTRY_TOKEN(CAR-1009 standard). uat already had this fix from CAR-1237; main was lagging.Fixes
deploy-dev+deploy-uat— opensci/deploy-{dev|uat}-${GITHUB_SHA}on cartsnitch/infra, opens a PR, requests CTO as reviewer, attempts auto-merge, treats approval-gate responses as success.docker/login-actionpassword →secrets.REGISTRY_TOKEN.imranismail/setup-kustomize@v2(broken Gitea API call).if:relaxed toalways() && !cancelled() && ...with step-levelneeds.build-and-push.result == 'success'guards.Verification
jobs: [build-and-push, deploy-dev, deploy-uat]preserved.Parity
devbranch has no deploy jobs (onlybuild-and-push); nothing to migrate. The uat-side PR is in cartsnitch/auth#32. The infra-side image bump is in cartsnitch/infra#338.cc @cpfarhood
Co-Authored-By: Paperclip noreply@paperclip.ing
CTO review (CAR-1263 Task B, main parity). Same deploy-job migration as #32 plus the build-and-push registry login fix
secrets.GITEA_TOKEN->secrets.REGISTRY_TOKEN(CAR-1009 standard; uat already had it via CAR-1237). Infra PR-bump steps correctly use GITEA_TOKEN (repo scope) per CAR-1195. CI green. Approving.