T

HoloPanio 83377a7d0d feat(ci): run dalpuri CW-to-API sync as a k8s Job before deploy

The CW MSSQL and API Postgres addresses are internal to the cluster and
unreachable from GitHub-hosted runners, so the sync must run inside k8s.

- Add dalpuri-sync Docker stage to api/Dockerfile: installs deps,
  generates both Prisma clients, and runs dalpuri/src/sync.ts
- Add dalpuri/kubernetes/sync-job.yaml: mounts api-env-secret (which
  already contains CW_DATABASE_URL) and maps DATABASE_URL -> API_DATABASE_URL
- build-api job now also pushes optima-dalpuri-sync:TAG image
- sync-cw-to-api CI job replaced with kubectl apply/wait pattern,
  needs [build-api, build-worker], blocks deploy-api and deploy-worker

2026-04-08 20:19:06 +00:00

.docker

all the haul

2026-04-07 23:56:31 +00:00

.github/workflows

feat(ci): run dalpuri CW-to-API sync as a k8s Job before deploy

2026-04-08 20:19:06 +00:00

.husky

ci(global): fix failing tests

2026-04-08 03:09:27 +00:00

api

feat(ci): run dalpuri CW-to-API sync as a k8s Job before deploy