Unity Catalog Schemas in Declarative Automation Bundles Are a Footgun

oieduardorabelo — Sun, 23 Aug 2026 01:34:11 GMT

Last week a teammate ran databricks bundle deploy against our dev workspace. It failed on a schema that already existed. She had not touched that schema. Nobody had. Her code was identical to mine, and my deploy had worked ten minutes earlier.

The cause is a mismatch that most teams never notice until it bites them. DAB deployment state is private, one file per developer under your own user folder.

Development mode normally keeps those two worlds apart by prefixing your schema name, so the moment you find skip_name_prefix_for_schema in the docs and switch it on, every developer's private state file starts claiming the same public object.

I wrote up what happens next, step by step, including the second hazard nobody expects. Then I go through 4 patterns that avoid the problem instead of hiding it and one of them needs no extra tooling at all.

Full write-up here: https://dev.to/oieduardorabelo/unity-catalog-schemas-in-declarative-automation-bundles-are-a-footgun-3o3e

topic Unity Catalog Schemas in Declarative Automation Bundles Are a Footgun in Community Articles

Unity Catalog Schemas in Declarative Automation Bundles Are a Footgun