feat(sql): Bundle Databricks SQLAlchemy dialect

[m1so]

Summary by CodeRabbit

• New Features

  • Added Databricks SQLAlchemy dialect support with Python-version-specific compatibility and a backward-compatible alias so databricks:// and databricks+connector:// both resolve.
  • Suppresses known third‑party deprecation warnings to reduce noisy warnings during SQL engine usage.

• Tests

  • Added tests for Databricks dialect registration and alias resolution.
  • Added tests verifying suppression of the third‑party deprecation warning.
  • Updated interrupt-handling test to simulate interruption during process checks.

• Chores

  • Expanded security audit ignore list to include CVE-2026-0994 and PYSEC-2024-161.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR adds Databricks SQLAlchemy dialect support by updating pyproject.toml with version-gated databricks-sqlalchemy dependencies and a new SQLAlchemy entry point mapping for "databricks.connector". CI workflow audit ignore list is expanded to include CVE-2026-0994 and PYSEC-2024-161. A context manager suppress_third_party_deprecation_warnings was introduced and applied when creating SQLAlchemy engines to suppress a known Databricks deprecation warning. Tests were added to verify both databricks:// and backward-compatible databricks+connector:// URL formats register and load correctly. One existing test (process cleanup on interrupt) was modified to raise KeyboardInterrupt from the process manager's check_processes call instead of simulating interruption via time.sleep.

Sequence Diagram(s)

sequenceDiagram
    participant App as Application / SQLAlchemy
    participant EP as EntryPoint Registry
    participant DBPkg as databricks.sqlalchemy
    participant DB as Databricks

    Note over App,EP: Resolve dialect from URL
    App->>EP: query "databricks" or "databricks+connector"
    EP-->>App: returns factory -> DBPkg:DatabricksDialect
    App->>DBPkg: import/load DatabricksDialect
    DBPkg-->>App: DatabricksDialect class
    App->>DB: connect using DatabricksDialect
    DB-->>App: connection established

Loading

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 77.78% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding Databricks SQLAlchemy dialect support by bundling dependencies and registering dialect entry points.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

Warning

Review ran into problems

🔥 Problems

Errors were encountered while retrieving linked issues.

Errors (2)

• CVE-2026: Entity not found: Issue - Could not find referenced Issue.
• PYSEC-2024: Entity not found: Issue - Could not find referenced Issue.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

📦 Python package built successfully!

• Version: 2.0.0.dev6+c1898bc
• Wheel: deepnote_toolkit-2.0.0.dev6+c1898bc-py3-none-any.whl
• Install:

  pip install "deepnote-toolkit @ https://deepnote-staging-runtime-artifactory.s3.amazonaws.com/deepnote-toolkit-packages/2.0.0.dev6%2Bc1898bc/deepnote_toolkit-2.0.0.dev6%2Bc1898bc-py3-none-any.whl"

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.28%. Comparing base (2eac218) to head (2b03f7c).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #61      +/-   ##
==========================================
+ Coverage   73.27%   73.28%   +0.01%     
==========================================
  Files          93       93              
  Lines        5193     5199       +6     
  Branches      757      757              
==========================================
+ Hits         3805     3810       +5     
- Misses       1144     1147       +3     
+ Partials      244      242       -2     

Flag	Coverage Δ
combined	73.28% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[deepnote-bot]

🚀 Review App Deployment Started

📝 Description	🌐 Link / Info
🌍 Review application	ra-61
🔑 Sign-in URL	Click to sign-in
📊 Application logs	View logs
🔄 Actions	Click to redeploy
🚀 ArgoCD deployment	View deployment
⏰ Last deployed	2026-01-27 14:32:43 (UTC)
📜 Deployed commit	a041b4d2eda24f8fd80bac78e5b2cbeef777e48e
🛠️ Toolkit version	c1898bc

[Artmann]

This is great! Now I can use my database integration directly :) I do get this warning, though:

[WARN] Parameter '_user_agent_entry' is deprecated; use 'user_agent_entry' instead. This parameter will be removed in the upcoming releases.

[m1so]

@Artmann I noticed that as well during testing on RA but forgot to commit a fix to suppress the warnings. See 2b03f7c for more context

[coderabbitai]

Actionable comments posted: 2

🤖 Fix all issues with AI agents

In `@deepnote_toolkit/sql/sql_execution.py`:
- Around line 443-462: Add an explicit return type to the context manager (e.g.,
-> Iterator[None]) and narrow the warnings.filterwarnings call to only suppress
DeprecationWarning so unrelated warnings aren't swallowed; update the
suppress_third_party_deprecation_warnings signature to include the type import
(Iterator) and change the warnings.filterwarnings(...) call to include
category=DeprecationWarning while keeping the existing message regex and yield
behavior.

In `@tests/unit/test_sql_execution.py`:
- Around line 958-986: In the test functions
test_does_not_suppress_unrelated_warnings and the earlier warning block, update
the calls to warnings.warn to include stacklevel=2 so Ruff B028 is satisfied and
the warning points at the test caller; locate the warnings.warn invocations
inside the with suppress_third_party_deprecation_warnings() context (and the
simulated databricks-sqlalchemy warning) and add the stacklevel=2 kwarg to each
call while leaving the message and category unchanged.