Databricks Emulator

Local emulator of a Databricks workspace in a single Go binary — PAT and this process’s own OIDC, workspace files, Jobs, SQL warehouses, and an attached Spark engine. The bet is the family’s: terminate the public REST, attach a real engine, refuse what you cannot compute. Entra is an optional federated issuer, not a required STS.

Caution

Local development tool only — self-signed TLS, a seeded admin PAT. It emulates the workspace contract, not a security boundary. Run it on localhost only. token=dev is 401.

Start here

• Doctrine — the founding constraint
• Quickstart — seeded PAT, official SDK Me, token=dev is 401
• Installation — source, GHCR, family compose
• Architecture — this process vs Sail vs UC vs vault
• Configuration — every DATABRICKS_* variable
• One toggle — DATABRICKS_TARGET=emulator\|real, names in, ids out
• TLS and hosts — self-signed cert, HTTP opt-out
• Identity — PAT, emulator OIDC, federated JWT
• Workspace and files — SOURCE/PYTHON, workspace-files, DBFS
• Jobs and the Spark attach — Sail; no engine means fail, never SUCCESS
• Secrets — persist, injection, AKV read-through
• SQL warehouses and MCP — dialect spark-sql, not Photon
• Clusters and Connect — session handle; gRPC URL is not the HTTP agent
• Unity Catalog — UC OSS proxy; grants stay 501
• Testing — what e2e-sdk / e2e-terraform / e2e-engine / e2e-delta / e2e-uc each prove
• Family integration — entra, keyvault, fabric activities, chain test
• Roadmap — next honest attaches; not implemented
• Parity ledger — catalog is the workspace REST API reference
• Parity history — snapshots from git tags