Skip to content

Skip Lakebase deploy if project already exists#493

Open
auschoi96 wants to merge 1 commit intodatabricks-solutions:mainfrom
auschoi96:fix/deploy-skip-existing-lakebase
Open

Skip Lakebase deploy if project already exists#493
auschoi96 wants to merge 1 commit intodatabricks-solutions:mainfrom
auschoi96:fix/deploy-skip-existing-lakebase

Conversation

@auschoi96
Copy link
Copy Markdown
Collaborator

Summary

  • databricks-builder-app/scripts/deploy.sh now checks databricks postgres get-project before running bundle deploy, so re-runs against a workspace where the Lakebase project already exists skip the deploy step instead of failing.
  • Lets users reuse an existing Lakebase instance without passing --skip-lakebase every time.

Test plan

  • Run ./scripts/deploy.sh in a workspace with no existing Lakebase project — step 2 deploys via DAB as before.
  • Re-run against the same workspace — step 2 reports "already exists — reusing" and continues.
  • Run with --skip-lakebase — still short-circuits to the skipped message.

This pull request and its description were written by Isaac.

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant