fix(ci): increase dalpuri sync timeout from 30min to 2h

Full initial sync has 500k+ rows across all tables and exceeded the
30-minute activeDeadlineSeconds. Bump both the k8s job deadline and
the kubectl wait timeout to 7200s (2 hours).

.github/workflows/deploy.yaml

@@ -293,7 +293,7 @@ jobs:
   # must succeed before either the API or worker deploys.
   sync-cw-to-api:
     name: Sync - CW to API
-    needs: [build-api, build-worker]
+    needs: [migrate-api, build-worker]
     runs-on: ubuntu-latest
     steps:
       - name: Set the Kubernetes context
@@ -318,9 +318,9 @@ jobs:
           TAG=${{ github.event.release.tag_name }}
           JOB="job/dalpuri-sync-${TAG}"
 
-          kubectl wait --for=condition=complete --timeout=1800s -n optima "$JOB" &
+          kubectl wait --for=condition=complete --timeout=7200s -n optima "$JOB" &
           WAIT_COMPLETE=$!
-          kubectl wait --for=condition=failed --timeout=1800s -n optima "$JOB" &
+          kubectl wait --for=condition=failed --timeout=7200s -n optima "$JOB" &
           WAIT_FAILED=$!
 
           wait -n $WAIT_COMPLETE $WAIT_FAILED

dalpuri/kubernetes/sync-job.yaml

@@ -8,7 +8,7 @@ metadata:
 spec:
   backoffLimit: 0
   ttlSecondsAfterFinished: 86400
-  activeDeadlineSeconds: 1800
+  activeDeadlineSeconds: 7200
   template:
     metadata:
       labels:
@@ -17,10 +17,12 @@ spec:
       containers:
         - name: sync
           image: ghcr.io/horizonstacksoftware/optima-dalpuri-sync:RELEASE_TAG
-          envFrom:
-            - secretRef:
-                name: api-env-secret
           env:
+            - name: CW_DATABASE_URL
+              valueFrom:
+                secretKeyRef:
+                  name: api-env-secret
+                  key: CW_DATABASE_URL
             - name: API_DATABASE_URL
               valueFrom:
                 secretKeyRef: