Uh oh!
There was an error while loading. Please reload this page.
Raise an error when volumes are used for paths other than artifacts - #2754
Merged
Conversation
andrewnester
requested review from
anton-107, denik, pietern and shreyas-goenka
as code ownersApril 23, 2025 11:30
andrewnestertemporarily deployed
to
test-trigger-is
April 23, 2025 11:30 — with 
GitHub Actions
Inactive
andrewnestertemporarily deployed
to
test-trigger-is
April 23, 2025 11:31 — with GitHub Actions
Inactive
andrewnester
enabled auto-merge
April 23, 2025 11:31
andrewnestertemporarily deployed
to
test-trigger-is
April 23, 2025 11:43 — with GitHub Actions
Inactive
pietern
reviewed
Apr 24, 2025
Uh oh!
There was an error while loading. Please reload this page.
| Error: workspace.state_path /Volumes/test/state starts with /Volumes. /Volumes can only be used with workspace.artifact_path. | ||
| Error: workspace.resource_path /Volumes/test/resources starts with /Volumes. /Volumes can only be used with workspace.artifact_path. |
Contributor
There was a problem hiding this comment.
Do we need to report all errors when specifying workspace.root_path?
ContributorAuthor
There was a problem hiding this comment.
Was debating this as well, in majority of the cases indeed make sense to report it only once
Uh oh!
There was an error while loading. Please reload this page.
pietern
commented
Apr 24, 2025
Contributor
Btw, the "volumes" name can be used uncapitalized. Ref: https://docs.databricks.com/aws/en/volumes/ |
andrewnestertemporarily deployed
to
test-trigger-is
April 24, 2025 09:28 — with GitHub Actions
Inactive
pietern
approved these changes
Apr 24, 2025
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pietern
disabled auto-merge
April 24, 2025 09:50
Co-authored-by: Pieter Noordhuis <pieter.noordhuis@databricks.com>
andrewnestertemporarily deployed
to
test-trigger-is
April 24, 2025 10:50 — with GitHub Actions
Inactive
andrewnestertemporarily deployed
to
test-trigger-is
April 24, 2025 10:54 — with GitHub Actions
Inactive
andrewnester
enabled auto-merge
April 24, 2025 10:54
deco-sdk-taggingBot
added a commit
that referenced
this pull request
Apr 30, 2025
## Release v0.250.0 ### Notable Changes * Added inline script execution support to bundle run. You can now run scripts in the same authentication context as a DAB using the databricks bundle run command. ([#2413](#2413)) ### Dependency updates * Upgrade TF provider to 1.75.0 ([#2775](#2775)) * Upgrade Go SDK to 0.65.0 ([#2786](#2786)) ### CLI * Added `databricks apps run-local` command to run Databricks apps locally ([#2555](#2555)) ### Bundles * Raise an error when Unity Catalog volumes are used for paths other than artifacts ([#2754](#2754)) * Fixed issue with jobs and pipelines declared in Python not showing in "Bundle resource explorer" in VSCode ([#2764](#2764)) * Made `experimental/python/mutators` and `experimental/python/resources` fields optional in JSON schema ([#2761](#2761)) * Annotated deprecated fields in JSON schema ([#2770](#2770))
denik pushed a commit
that referenced
this pull request
May 20, 2026
…2754) ## Changes Raise an error when volumes are used for paths other than artifacts. ## Why `/Volumes/...` paths can only be used for `workspace.artifact_path` at the moment. When used in other places, we should raise an error because it's an incorrect configuration. ## Tests Added an acceptance test --------- Co-authored-by: Pieter Noordhuis <pieter.noordhuis@databricks.com>
denik pushed a commit
that referenced
this pull request
May 20, 2026
## Release v0.250.0 ### Notable Changes * Added inline script execution support to bundle run. You can now run scripts in the same authentication context as a DAB using the databricks bundle run command. ([#2413](#2413)) ### Dependency updates * Upgrade TF provider to 1.75.0 ([#2775](#2775)) * Upgrade Go SDK to 0.65.0 ([#2786](#2786)) ### CLI * Added `databricks apps run-local` command to run Databricks apps locally ([#2555](#2555)) ### Bundles * Raise an error when Unity Catalog volumes are used for paths other than artifacts ([#2754](#2754)) * Fixed issue with jobs and pipelines declared in Python not showing in "Bundle resource explorer" in VSCode ([#2764](#2764)) * Made `experimental/python/mutators` and `experimental/python/resources` fields optional in JSON schema ([#2761](#2761)) * Annotated deprecated fields in JSON schema ([#2770](#2770))
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
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.
Changes
Raise an error when volumes are used for paths other than artifacts.
Why
/Volumes/...paths can only be used forworkspace.artifact_pathat the moment. When used in other places, we should raise an error because it's an incorrect configuration.Tests
Added an acceptance test