fix(dalpuri): populate userIdentifiersByMemberRecId from CwMember table

When no User accounts have cwMemberId linked, the context map was empty and all opportunities got primarySalesRepId = null. Now also populate the map from CwMember rows directly (User-linked entries take precedence), so rep identifiers resolve correctly regardless of user account linkage.
fix(dalpuri): exit(0) after sync completes to release k8s job
2026-04-08 23:23:51 +00:00 · 2026-04-08 21:50:52 +00:00 · 2026-04-08 21:19:43 +00:00 · 2026-04-08 20:41:49 +00:00 · 2026-04-08 20:27:05 +00:00
4 changed files with 49 additions and 11 deletions
@@ -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
@@ -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:
@@ -294,6 +294,22 @@ const refreshContextFromApi = async (
    }
  }

+  const cwMembers = await apiPrisma.cwMember.findMany({
+    select: { cwMemberId: true, identifier: true },
+  });
+  for (const member of cwMembers) {
+    if (
+      member.cwMemberId != null &&
+      member.identifier &&
+      !context.userIdentifiersByMemberRecId.has(member.cwMemberId)
+    ) {
+      context.userIdentifiersByMemberRecId.set(
+        member.cwMemberId,
+        member.identifier
+      );
+    }
+  }
+
  for (const board of boards) {
    context.serviceTicketBoardUidsById.set(board.id, board.uid);
  }
@@ -323,6 +323,22 @@ const refreshContextFromApi = async (
    }
  }

+  const cwMembers = await apiPrisma.cwMember.findMany({
+    select: { cwMemberId: true, identifier: true },
+  });
+  for (const member of cwMembers) {
+    if (
+      member.cwMemberId != null &&
+      member.identifier &&
+      !context.userIdentifiersByMemberRecId.has(member.cwMemberId)
+    ) {
+      context.userIdentifiersByMemberRecId.set(
+        member.cwMemberId,
+        member.identifier
+      );
+    }
+  }
+
  for (const board of boards) {
    context.serviceTicketBoardUidsById.set(board.id, board.uid);
  }
@@ -1860,7 +1876,11 @@ export const executeForcedIncrementalDalpuriSync = async (options?: {
 };

 if (import.meta.main) {
-  executeFullDalpuriSync().catch((error) => {
+  executeFullDalpuriSync()
+    .then(() => {
+      process.exit(0);
+    })
+    .catch((error) => {
      console.error("CW -> API sync failed:", error);
      process.exit(1);
    });
Author	SHA1	Message	Date
HoloPanio	1233535b20	fix(dalpuri): populate userIdentifiersByMemberRecId from CwMember table When no User accounts have cwMemberId linked, the context map was empty and all opportunities got primarySalesRepId = null. Now also populate the map from CwMember rows directly (User-linked entries take precedence), so rep identifiers resolve correctly regardless of user account linkage.	2026-04-08 23:23:51 +00:00
HoloPanio	2c737b22f1	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.	2026-04-08 21:50:52 +00:00
HoloPanio	a3bfe9f374	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).	2026-04-08 21:19:43 +00:00
HoloPanio	a106bb15a8	fix(ci): explicit env vars in dalpuri sync job; add CW_DATABASE_URL to secret envFrom was loading api-env-secret but CW_DATABASE_URL was absent from the deployed secret, causing sync.ts to fall back to DATABASE_URL (Postgres) as the MSSQL connection string -> 'Invalid port number: //optima'. - Replaced envFrom with explicit CW_DATABASE_URL and API_DATABASE_URL env entries so the mapping is unambiguous - Patched api-env-secret in cluster to add CW_DATABASE_URL	2026-04-08 20:41:49 +00:00
HoloPanio	d9a431d99a	fix(ci): sync-cw-to-api must wait for migrate-api to complete Migration must finish before sync runs so the schema exists.	2026-04-08 20:27:05 +00:00