Skip to content

docs: repoint the Databricks masking links to the new connection pages #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
beneboy merged 1 commit into from
Sep 8, 2026
Merged

docs: repoint the Databricks masking links to the new connection pages #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading