From 2c737b22f104a7658870daae728a7974bddc3793 Mon Sep 17 00:00:00 2001
From: Jackson Roberts <jrobe3221@gmail.com>
Date: Wed, 8 Apr 2026 21:50:52 +0000
Subject: [PATCH] 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.
---
 dalpuri/src/sync.ts | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/dalpuri/src/sync.ts b/dalpuri/src/sync.ts
index cb89f8f..6465a71 100644
--- a/dalpuri/src/sync.ts
+++ b/dalpuri/src/sync.ts
@@ -1860,8 +1860,12 @@ export const executeForcedIncrementalDalpuriSync = async (options?: {
 };
 
 if (import.meta.main) {
-  executeFullDalpuriSync().catch((error) => {
-    console.error("CW -> API sync failed:", error);
-    process.exit(1);
-  });
+  executeFullDalpuriSync()
+    .then(() => {
+      process.exit(0);
+    })
+    .catch((error) => {
+      console.error("CW -> API sync failed:", error);
+      process.exit(1);
+    });
 }