[Internal] Use resolved host type from metadata in host_type property#1372
Open
[Internal] Use resolved host type from metadata in host_type property#1372
Conversation
Signed-off-by: Tanmay Rustagi <tanmay.rustagi@databricks.com>
tanmay-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
tanmay-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
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>
tanmay-db
force-pushed
the
hosttype-resolved
branch
from
6aabd40 to
5b45243
Compare
tanmay-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
tanmay-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
tanmay-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
tanmay-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
tanmay-db
changed the title
Align the field name with the API contract for the well-known databricks-config endpoint. Co-authored-by: Isaac
tanmay-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
tanmay-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
The API returns this field as an array of strings. Use the first element when resolving token_audience. Co-authored-by: Isaac
tanmay-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
tanmay-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
|
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. |
tanmay-db
had a problem deploying
to
test-trigger-is
GitHub Actions
Failure
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
1 participant
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.
🥞 Stacked PR
Use this link to review incremental changes.
Changes
Changes
Wire the resolved host type from metadata into the
host_typeproperty:Config.host_typeto return_resolved_host_type(from the/.well-known/databricks-configdiscovery endpoint) when available,falling back to the existing URL-based pattern matching when metadata is
unavailable.
the new behavior.
This means
host_typenow correctly returnsHostType.UNIFIEDforunified hosts, and can distinguish account vs workspace hosts based on
server metadata rather than URL patterns alone.
Tests
host_type=workspaceoverrides an account-like URL pattern.host_type=accountoverrides a workspace-like URL pattern.host_type=unifiedis correctly returned.host_typeis missingor unrecognized.
host_typeproperty returnsmetadata value over URL matching.