Skip to content
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.

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

Adjust useDatabricksOAuthInAzure behavior #225

Merged
merged 2 commits into from
Feb 5, 2024

Conversation

kravets-levko
Copy link
Contributor

useDatabricksOAuthInAzure = true means that user wants to use Databricks OAuth method on given Azure instance. And if that Azure host is not supported - we shouldn't silently fall back to Azure OAuth but throw an error instead. Azure OAuth should be used only when useDatabricksOAuthInAzure = false

@codecov-commenter
Copy link

codecov-commenter commented Feb 1, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (4d4078b) 90.61% compared to head (4aec809) 90.61%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #225   +/-   ##
=======================================
  Coverage   90.61%   90.61%           
=======================================
  Files          62       62           
  Lines        1439     1439           
  Branches      246      246           
=======================================
  Hits         1304     1304           
  Misses         84       84           
  Partials       51       51           

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

Signed-off-by: Levko Kravets <levko.ne@gmail.com>
@kravets-levko kravets-levko merged commit 3953e5d into main Feb 5, 2024
8 checks passed
@kravets-levko kravets-levko deleted the adjust-useDatabricksOAuthInAzure-behaviour branch February 5, 2024 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants