Uh oh!
There was an error while loading. Please reload this page.
[apps-mcp] Fix token-based authentication for default profile - #4195
Merged
Conversation
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
lennartkats-dbtemporarily deployed
to
test-trigger-is
January 5, 2026 08:49 — with 
GitHub Actions
Inactive
Collaborator
Commit: 4df311d
19 interesting tests: 14 KNOWN, 4 RECOVERED, 1 SKIP
Top 33 slowest tests (at least 2 minutes):
|
fjakobs
approved these changes
Jan 5, 2026
eng-dev-ecosystem-bot
commented
Jan 5, 2026
Collaborator
Commit: 56fc0db
26 interesting tests: 14 KNOWN, 5 flaky, 4 RECOVERED, 2 FAIL, 1 SKIP
Top 50 slowest tests (at least 2 minutes):
|
pietern added a commit
that referenced
this pull request
Jan 12, 2026
…moval The secret scope permissions test fails ~33% of the time when using the Terraform bundle engine. The root cause is a backend API race condition where parallel ACL modifications return inconsistent results. The direct bundle engine already works around this by sequentializing ACL operations (see #3886): // Set ACLs. The service returns inconsistent results for parallel // API calls. That's why we do them sequentially here to maintain // correctness. The Terraform provider has a similar workaround for creates via robustPutACL with retry/verification (terraform-provider-databricks#4885, issue #4195), but deletions have no such protection. This change adds a depends_on chain between ACL resources, forcing Terraform to execute them sequentially: ACL_0 → depends_on: [scope] ACL_1 → depends_on: [scope, ACL_0] ACL_2 → depends_on: [scope, ACL_1] This avoids triggering the backend race condition without requiring changes to the Terraform provider. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
denik pushed a commit
that referenced
this pull request
May 20, 2026
# [apps-mcp] Fix token-based authentication for default profile ## Changes Fix authentication in `apps-mcp` for the `DEFAULT` profile. ## Why When `InvokeDatabricksCLI` runs a subprocess, it sets `DATABRICKS_HOST` explicitly. This prevents the SDK from falling back to the DEFAULT profile in `~/.databrickscfg`, causing auth failures. The old code tried to pass `DATABRICKS_CONFIG_PROFILE`, but `GetDatabricksProfile()` always returned empty because the profile was never stored in the session during auto-authentication. Passing the token directly works for all auth methods (OAuth, PAT, profile-based). ## Tests Manual testing via MCP server: ```bash # Without fix: auth error agent -p 'invoke databricks cli with "current-user me"' # ✗ # With fix: succeeds agent -p 'invoke databricks cli with "current-user me"' # ✓ ``` Root cause confirmed by reproducing SDK behavior directly: ```bash # SDK falls back to DEFAULT profile when no host is set ./cli current-user me # ✓ # SDK fails when DATABRICKS_HOST is set without credentials DATABRICKS_HOST=https://... ./cli current-user me # ✗ ``` OAuth-based auth also works since `Config.Token` is populated with the OAuth access token after authentication. 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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
[apps-mcp] Fix token-based authentication for default profile
Changes
Fix authentication in
apps-mcpfor theDEFAULTprofile.Why
When
InvokeDatabricksCLIruns a subprocess, it setsDATABRICKS_HOSTexplicitly. This prevents the SDK from falling back to the DEFAULT profile in~/.databrickscfg, causing auth failures.The old code tried to pass
DATABRICKS_CONFIG_PROFILE, butGetDatabricksProfile()always returned empty because the profile was never stored in the session during auto-authentication.Passing the token directly works for all auth methods (OAuth, PAT, profile-based).
Tests
Manual testing via MCP server:
Root cause confirmed by reproducing SDK behavior directly:
OAuth-based auth also works since
Config.Tokenis populated with the OAuth access token after authentication.