Skip to content

feat: bump databricks-sdk v0.1.7 and rename RefreshableCredentials to SessionCredentials#349

Merged
susodapop merged 3 commits intodatabricks:staging-349from
pavs23:bump-databricks-sdk
May 18, 2023
Merged

feat: bump databricks-sdk v0.1.7 and rename RefreshableCredentials to SessionCredentials#349
susodapop merged 3 commits intodatabricks:staging-349from
pavs23:bump-databricks-sdk

Conversation

@pavs23
Copy link
Copy Markdown
Contributor

@pavs23 pavs23 commented May 17, 2023

This resolves this issue I raised recently #348

Root cause is due to the renaming done in this PR: databricks/databricks-sdk-py#116

These types of breaking changes are normal and part of life. Would like to see this get pushed through ASAP though.

Description

  • Bump to the databricks-sdk to use the latest version.
  • Rename the RefreshableCredentials references to SessionCredentials

It would be failing for anyone trying to connect to databricks using dbt-core and the dbt-databricks adapter if I'm not mistaken.

Checklist

  • I have run this code in development and it appears to resolve the stated issue
  • This PR includes tests, or tests are not required/relevant for this PR
  • I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.

@pavs23 pavs23 changed the title feat: bump databricks-sdk version to v0.1.7 feat: bump databricks-sdk v0.1.7 and rename RefreshableCredentials to SessionCredentials May 17, 2023
Copy link
Copy Markdown

@susodapop susodapop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You need to change the databricks-sdk dependency spec in setup.py, else this won't affect the dependency map that pip builds during installation.

I had to incorporate these same changes into #338 so you can see exactly where the changes are needed.

Happy to merge your PR instead and rebase my change on yours though 🚀

@pavs23
Copy link
Copy Markdown
Contributor Author

pavs23 commented May 18, 2023

Hey @susodapop , thanks for the feedback.
Good spot, I've updated the PR. Ready to merge when you are!

@susodapop susodapop changed the base branch from main to staging-349 May 18, 2023 22:55
Copy link
Copy Markdown

@susodapop susodapop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! Per the CONTRIBUTING guide, I've updated this PR to hit a staging branch so we can run our e2e tests before merging to main.

@pavs23
Copy link
Copy Markdown
Contributor Author

pavs23 commented May 18, 2023

Thanks @susodapop :)

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.

2 participants