Draft
Conversation
Signed-off-by: Tanmay Rustagi <tanmay.rustagi@databricks.com>
This was referenced Mar 30, 2026
Signed-off-by: Tanmay Rustagi <tanmay.rustagi@databricks.com>
Signed-off-by: Tanmay Rustagi <tanmay.rustagi@databricks.com>
Signed-off-by: Tanmay Rustagi <tanmay.rustagi@databricks.com>
6aabd40 to
5b45243
Compare
|
If integration tests don't run automatically, an authorized user can run them manually by following the instructions below: Trigger: Inputs:
Checks will be approved automatically on success. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Python SDK — PR #1372: [Internal] Use resolved host type from host metadata in host_type
property
🥞 Stacked PR
Use this [link](https://github.com/databricks/databricks-sdk-py/pull/1372/files/ca751eebb5ffcd
689c678475b0f60bcf8c4180da..6aabd40) to review incremental
changes.
changed]
changed](https://github.com/Default OIDC audience #1371/files/f48e10283426bda51b2e
f18c218ec019d51de3c9..ca751ee)]
[[Files changed](https://github.com/Hosttype resolved #1372/files/ca751eebb5ffc
d689c678475b0f60bcf8c4180da..6aabd40)]
Summary
The
host_typeproperty now returns the host type resolved from host metadata when available,falling back to URL pattern matching only when metadata has not been resolved.
Why
PRs #1370 and #1371 added
host_typeparsing toHostMetadataand store it inConfig._resolved_host_type. However, thehost_typeproperty still relied solely on URLpattern matching. This meant the authoritative signal from the server was ignored.
URL pattern matching is fragile — it can't distinguish unified hosts, and custom or
non-standard URLs may not follow expected patterns. The metadata endpoint is the authoritative
source, so
host_typeshould prefer it.What changed
Interface changes
None.
host_typestill returnsHostTypewith the same possible values.Behavioral changes
host_typenow returns_resolved_host_typewhen it is notNone, taking priorityover all existing fallback logic (including URL pattern matching).
_resolved_host_type is None), behavior is identical tobefore.
Internal changes
_resolved_host_typecheck at top ofhost_typeproperty inconfig.py.How is this tested?
7 new tests:
NO_CHANGELOG=true