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.
Adds tests covering: - DATABRICKS_DISCOVERY_URL env var is loaded into Config - getDatabricksOidcEndpoints() short-circuits to discoveryUrl when set The underlying implementation (discoveryUrl config field and getDatabricksOidcEndpoints() short-circuit) was already present in the Java SDK. Mirrors the Python SDK's get_endpoints_from_url() addition.
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
This was referenced Feb 25, 2026
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
hectorcast-db
changed the title
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
|
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. |
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
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.
Summary
Adds tests covering OIDC endpoint resolution directly from a discovery URL, exercising the existing
discoveryUrlconfig field and thegetDatabricksOidcEndpoints()short-circuit path.Why
The OIDC discovery URL returned by
/.well-known/databricks-configpoints to a standard OAuth 2.0 authorization server metadata document (authorization_endpoint,token_endpoint). The Java SDK already hasdiscoveryUrl(DATABRICKS_DISCOVERY_URL) andgetDatabricksOidcEndpoints()fetching directly from it when set — this is the Java equivalent of the Python SDK'sget_endpoints_from_url()addition. This PR adds the missing test coverage for those paths.What changed
Interface changes
None. The
discoveryUrlconfig field (DATABRICKS_DISCOVERY_URL) and thegetDatabricksOidcEndpoints()short-circuit were already present in the Java SDK.Behavioral changes
None. No existing code paths are modified.
Internal changes
testDiscoveryUrlFromEnv— verifiesDATABRICKS_DISCOVERY_URLenv var is loaded intodiscoveryUrl.testDatabricksOidcEndpointsUsesDiscoveryUrl— verifiesgetDatabricksOidcEndpoints()short-circuits to fetch directly fromdiscoveryUrlwhen set.How is this tested?
Unit tests in
DatabricksConfigTestusingFixtureServer.NO_CHANGELOG=true