refactor(spark): isolate Databricks PAT authentication - #3452
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3452 +/- ##
=======================================
Coverage 47.79% 47.79%
=======================================
Files 217 217
Lines 22943 22943
Branches 3036 3036
=======================================
Hits 10966 10966
Misses 11370 11370
Partials 607 607 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Hosted CI is complete. Every check relevant to this change, including The sole failure is I do not have permission to rerun that job. I am leaving this PR in draft as promised until a maintainer can rerun or confirm the unrelated baseline failure. |
Introduce an authentication strategy boundary while preserving the existing PAT resolution and connector behavior, enabling subsequent auth methods to be reviewed independently. Signed-off-by: Rohit Sharma <rohitrsh@gmail.com>
b787704 to
ecfd142
Compare
Summary
DatabricksAuthstrategy interface and aPATAuthimplementation.This is the first of four smaller changes superseding #3429:
No new authentication mode, task configuration, or Kubernetes permission is introduced here. This also contributes to flyteorg/flyte#7319.
Test plan
pytest tests/test_databricks_auth.py tests/test_databricks_token.py tests/test_connector.py -q— 49 passedmake lintmake unit_test_codecov— 1,982 passed, 23 skippedgit diff --checkThe PR is draft until all hosted checks are green.