Fix WSFS extensions for cross-workspace deployments #3516
+50
−0
Conversation
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
When running DABS from within a Databricks workspace with files under /Workspace/, the CLI would incorrectly use WSFS extensions even when deploying to a different workspace. This caused "path does not exist" errors because it tried to read files from the current workspace while deploying to the target workspace. The fix adds cross-workspace deployment detection by comparing the current workspace host (DATABRICKS_HOST env var) with the target workspace host from the bundle configuration. When hosts differ, WSFS extensions are skipped and the standard workspace files client is used instead. This resolves customer issues where dynamically generated DABS configurations work within the same workspace but fail when targeting a different workspace. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
fjakobs
requested review from
pietern,
andrewnester,
shreyas-goenka,
denik and
anton-107
as code owners
fjakobs
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
10 failing tests:
|
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.
When running DABS from within a Databricks workspace with files under /Workspace/, the CLI would incorrectly use WSFS extensions even when deploying to a different workspace. This caused "path does not exist" errors because it tried to read files from the current workspace while deploying to the target workspace.
The fix adds cross-workspace deployment detection by comparing the current workspace host (DATABRICKS_HOST env var) with the target workspace host from the bundle configuration. When hosts differ, WSFS extensions are skipped and the standard workspace files client is used instead.
This resolves customer issues where dynamically generated DABS configurations work within the same workspace but fail when targeting a different workspace.
🤖 Generated with Claude Code
Changes
Why
Tests