From 03c29954f2c9f05c285471c5baae432858de9164 Mon Sep 17 00:00:00 2001
From: CAholder <austinchoi@yahoo.com>
Date: Fri, 24 Apr 2026 12:06:17 -0700
Subject: [PATCH] Skip Lakebase deploy if project already exists

Check for an existing Lakebase project via `databricks postgres get-project`
before running `bundle deploy`, so re-runs against an existing instance are
idempotent instead of failing.

Co-authored-by: Isaac
---
 databricks-builder-app/scripts/deploy.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/databricks-builder-app/scripts/deploy.sh b/databricks-builder-app/scripts/deploy.sh
index 4fb6f5eb..997bbcd4 100755
--- a/databricks-builder-app/scripts/deploy.sh
+++ b/databricks-builder-app/scripts/deploy.sh
@@ -177,6 +177,8 @@ echo -e "${YELLOW}[2/${TOTAL_STEPS}] Deploying Lakebase...${NC}"
 
 if [ "$SKIP_LAKEBASE" = true ]; then
   echo -e "  ${GREEN}✓${NC} Skipped (--skip-lakebase)"
+elif databricks postgres get-project "projects/${LAKEBASE_PROJECT_ID}" $CLI_ARGS &> /dev/null; then
+  echo -e "  ${GREEN}✓${NC} Lakebase project '${LAKEBASE_PROJECT_ID}' already exists — reusing"
 else
   cd "$PROJECT_DIR"
   BUNDLE_ARGS=""