Docs · 06
Permissions & limits
The smallest set of grants bricksentry needs, and what v0.1 can't do yet.
Permissions
| Grant | Why |
|---|---|
CAN USE on a SQL warehouse | All diffs run as SQL there. |
SELECT on assessed tables and candidates | To compare production and the change. |
SELECT on system.access.table_lineage and system.information_schema | Blast radius, owners and tags. Without them it still diffs; lineage is empty. |
CREATE TABLE on sandbox_schema | Shallow clones for preview_write. |
Known limits (v0.1)
- Lineage is recorded at runtime, so brand-new tables have no downstream history yet.
- RDD operations aren't captured in lineage, and UDFs hide column mapping.
- Key columns are required for every table.
- Changed-table detection uses path globs.
- The Databricks backend is tested against a mocked SDK, so try it on a dev workspace first.