fix(dalpuri): exit(0) after sync completes to release k8s job

Prisma MSSQL adapter keeps connections open after the sync finishes,
preventing the process from exiting naturally. The k8s job was staying
in Running state indefinitely. Call process.exit(0) on success so the
job completes and the GH workflow step passes.

.github/workflows/deploy.yaml

@@ -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:

dalpuri/src/sync.ts

@@ -1860,8 +1860,12 @@ export const executeForcedIncrementalDalpuriSync = async (options?: {
 };
 
 if (import.meta.main) {
-  executeFullDalpuriSync().catch((error) => {
+  executeFullDalpuriSync()
-    console.error("CW -> API sync failed:", error);
+    .then(() => {
-    process.exit(1);
+      process.exit(0);
-  });
+    })
+    .catch((error) => {
+      console.error("CW -> API sync failed:", error);
+      process.exit(1);
+    });
 }