Open
Conversation
Add integration tests for Databricks Service Principal (M2M) and Azure Client Secret authentication types. This increases coverage for existing Auth types by adding: - Workspace OAuth M2M authentication test - Workspace Azure Client Secret authentication test - Account OAuth M2M authentication test - Account Azure Client Secret authentication test These tests verify that authentication works correctly by making API calls and validating responses. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
hectorcast-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
hectorcast-db
force-pushed
the
add-oidc-auth-tests
branch
from
132f54c to
375405f
Compare
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
tanmay-db
approved these changes
Feb 10, 2026
| import org.slf4j.LoggerFactory; | ||
|
|
||
| @ExtendWith(EnvTest.class) | ||
| @EnvContext("ucws") |
Contributor
There was a problem hiding this comment.
we are running this only for ucws?
github-merge-queue bot
pushed a commit
that referenced
this pull request
Feb 10, 2026
## What changes are proposed in this pull request? Fix getOidcEndpoints() method. The method was incorrectly returning Azure OIDC when `ARM_CLIENT_ID` is set, but `getOidcEndpoints()` is never called for Azure OIDC. This logic actually caused Databricks M2M to use the wrong endpoint when the user set the `ARM_CLIENT_ID` for other purposes as can be seen in #656 NOTE: The new logic **matches the behavior of the Go SDK**. ## How is this tested? - Before this change, M2M authentication would fail (see #656) - Add new tests and rerun existing ones. NO_CHANGELOG=true --------- Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
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
2 participants
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.
What changes are proposed in this pull request?
Add integration tests for Databricks Service Principal (M2M) and Azure Client Secret authentication types.
This increases coverage for existing Auth types by adding:
These tests verify that authentication works correctly by making API calls and validating responses.
This PR mirrors the changes from databricks/databricks-sdk-go#1470
How is this tested?
Run integration tests with appropriate environment variables set.
NO_CHANGELOG=true