Databricks assets grouped by target family:
s3/: Databricks consuming the existing S3 export pathdelta/: Databricks-first assets where Convex changes land directly in Unity Catalog Delta tables
flowchart LR
S3[S3-backed path]
Delta[Databricks Delta path]
S3 --> Views[Unity Catalog views over S3 parquet]
Delta --> Bronze[bronze CDC Delta]
Delta --> Silver[silver current-state Delta]
Use these assets the same way as the AWS templates:
- Snapshot them into
.memory/. - Edit the copied files there when Terraform state or generated artifacts are involved.
- Run from the copied directory, not from the repo checkout.
Recommended entrypoint: just databricks-template-snapshot
The S3-backed Databricks integration preserves the existing export workflow.
s3/terraform/unity_catalog_s3_external_location/: storage credentials, external location, grantss3/sql/register_staging_views.sql.tmpl: stableVIEWs overstaging/current/...parquet files
This template assumes:
- the AWS IAM role already exists, or
- you intentionally bootstrap with
skip_validation = true, then update the AWS trust policy and re-apply withskip_validation = false
The S3-backed landing sync now performs a preflight check against Unity Catalog
external locations. The published staging/current root must be covered by an
external location before read_files(...) views are applied.
Read more: platform/databricks/s3/README.md
The Databricks-first assets are the starting point for direct Delta landing.
delta/extractor/: a Databricks job entrypoint that mirrors the current Convex snapshot/delta checkpoint logic and writes bronze CDC tablesdelta/lakeflow/: Lakeflow SQL templates that turn bronze CDC tables into silver current-state tablesdelta/sql/: bootstrap DDL for schemas and control tablesdelta/resources/: Databricks bundle job definitions
The provider is configured from ~/.databrickscfg by default, typically using
the DEFAULT profile.
Read more: platform/databricks/delta/README.md