You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use DABs to deploy workflow jobs that run python_wheel_tasks from the package loaded using the tasks libraries as a whl artifact with a requirements txt file. Both the whl and the requirements txt files are loaded providing the local relative path to them from the workflow yml where they are referenced, to the repository local folder where they are located.
Please list the steps required to reproduce the issue, for example:
Run databricks bundle deploy ...
Run databricks bundle run ...
See error from the cluster driver:
run failed with error message [LibraryInstallationError]
Library installation failed for library due to user error. Error messages:
Requirements file must be stored in UC Volumes, dbfs, s3, adls, gs or as a workspace file/local file. Make sure the URI begins with 'dbfs:', 'file:', 's3:', 'abfss:', 'gs:', 'wasbs:', '/Volumes', or '/Workspace'but the URI is '/Shared/.bundle/target/ingest/files/deps/requirements.txt').
Expected Behavior
The dependent libraries requirements file path should be similar to the one of the deployed library whl artifact:
## Changes
Due to platform changes, all libraries, notebooks and etc. paths used in
Databricks must be started with either /Workspace or /Volumes prefix.
This PR makes sure that all bundle paths are correctly prefixed.
Note: this change is a breaking change if user previously configured and
used `/Workspace/Workspace` folder in their workspace file system or
having `/Workspace/${workspace.root_path}...` pattern configured
anywhere in their bundle config
Fixes: #1751
AI:
- [x] Scan DABs config and error out on
`/Workspace/${workspace.root_path}...` pattern usage
## Tests
Added unit tests
---------
Co-authored-by: Pieter Noordhuis <[email protected]>
Describe the issue
We use DABs to deploy workflow jobs that run
python_wheel_task
s from the package loaded using the taskslibraries
as awhl
artifact with arequirements
txt file. Both thewhl
and therequirements
txt files are loaded providing the local relative path to them from the workflowyml
where they are referenced, to the repository local folder where they are located.Configuration
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
databricks bundle deploy ...
databricks bundle run ...
Expected Behavior
The dependent libraries requirements file path should be similar to the one of the deployed library whl artifact:
like this:
Actual Behavior
The path to the requirements file is in fact:
OS and CLI version
Databricks CLI: v0.227.1
OS: Debian - Ubuntu 22.04
Is this a regression?
I think this was supposed to be fixed in this PR:
#1543
The text was updated successfully, but these errors were encountered: