From d8a6dcac1dd04690b674c399b42a9324a23452f1 Mon Sep 17 00:00:00 2001 From: Ben Shaw Date: Tue, 8 Sep 2026 16:10:52 +1200 Subject: [PATCH] docs: repoint the Databricks masking links to the new connection pages The DataMasque User Guide splits its single Databricks page into one page per connection type, so `databricks.html` no longer exists. Link to the Databricks SQL Warehouse and Databricks Lakebase connection pages instead. Positioning is unchanged: native masking stays the recommended default and masque-bricks stays the retained out-of-place option. --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e2c7d4b..2bf31b1 100644 --- a/README.md +++ b/README.md @@ -24,9 +24,9 @@ table untouched and produces a separate masked copy. Databricks data *in place* using a SQL Warehouse — covering Delta tables and Lakebase — without copying data out to S3 and back. If your tables fit the in-place model, prefer it: fewer moving parts, no S3 round-trip, no second copy -to manage. See the DataMasque -[native Databricks masking docs](https://datamasque.com/portal/documentation/latest/databricks.html) -for setup. +to manage. For setup, see the DataMasque connection docs for +[Databricks SQL Warehouse](https://datamasque.com/portal/documentation/latest/database-connections/databricks-sql-warehouse.html) +and [Databricks Lakebase](https://datamasque.com/portal/documentation/latest/database-connections/databricks-lakebase.html). **masque-bricks is the retained out-of-place option.** It is *not* deprecated. Use it when in-place masking does not fit your case — for example when you need