From a106bb15a84fb8c4cff3d6fb97fb1c24d6693c32 Mon Sep 17 00:00:00 2001
From: Jackson Roberts <jrobe3221@gmail.com>
Date: Wed, 8 Apr 2026 20:41:49 +0000
Subject: [PATCH] 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
---
 dalpuri/kubernetes/sync-job.yaml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/dalpuri/kubernetes/sync-job.yaml b/dalpuri/kubernetes/sync-job.yaml
index 6d2a837..69672d0 100644
--- a/dalpuri/kubernetes/sync-job.yaml
+++ b/dalpuri/kubernetes/sync-job.yaml
@@ -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: