Open
Conversation
Adds `HostMetadata` and a package-private `getHostMetadata()` on
`DatabricksConfig` for parsing the `/.well-known/databricks-config`
discovery endpoint.
The method returns raw metadata with no substitution (e.g.
`{account_id}` placeholders are left as-is), keeping it a pure
discovery primitive. Callers decide how to interpret the result.
This was referenced Feb 25, 2026
|
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.
🥞 Stacked PR
Use this link to review incremental changes.
Summary
Adds
HostMetadataand a package-privategetHostMetadata()onDatabricksConfigfor parsing the/.well-known/databricks-configdiscovery endpoint.Why
Databricks hosts expose a standard
/.well-known/databricks-configendpoint that returns the OIDC endpoint, account ID, and workspace ID in a single request. The SDK had no primitive to consume it — OIDC endpoint discovery was handled entirely through host-type-specific logic that requires the caller to already know whether the host is a workspace, account console, or unified host.This PR introduces the foundational building block: a
HostMetadataclass and a package-privategetHostMetadata()onDatabricksConfigthat fetches and parses the endpoint. The method returns raw metadata with no substitution (e.g.{account_id}placeholders are left as-is), keeping it a pure discovery primitive. Callers decide how to interpret the result.What changed
Interface changes
HostMetadata— New class incom.databricks.sdk.core.oauthwith fieldsoidcEndpoint,accountId,workspaceId. Deserialized from JSON via Jackson.DatabricksConfig.getHostMetadata()(package-private) — Fetches{host}/.well-known/databricks-configand returns aHostMetadata. ThrowsDatabricksExceptionon any HTTP error.Behavioral changes
None. No existing code paths are modified.
Internal changes
Tests in
DatabricksConfigTestcovering the two response shapes (workspace with static OIDC endpoint, account host with{account_id}template) and the HTTP error path.How is this tested?
Unit tests in
DatabricksConfigTestusingFixtureServer. Both workspace and account host response shapes are exercised, plus an HTTP error case.NO_CHANGELOG=true