We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
databricks_library
See https://docs.databricks.com/en/libraries/workspace-files-libraries.html
The databricks_library provider should have a workspace block taking a path to the workspace file.
workspace
path
This is particularly relevant given DBR15's ability to support requirements.txt files
requirements.txt
Sample syntax:
library { # https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/job#library-configuration-block workspace { path = databricks_workspace_file.requirements.workspace_path } }
If no support is planned (or not planned for a while), the documentation should be updated to reflect this rather than the conspicuous absence.
(The same happens to be true for volume files, too, which could be repeated verbatim as above with a text replacement. https://docs.databricks.com/en/libraries/volume-libraries.html )
The text was updated successfully, but these errors were encountered:
Document support of requirements.txt specification in cluster libra…
bb22a16
…ries Support for `requirements` parameter came via SDK, but documentation was missing. Fixes #3471
867f829
…ries (#3637) Support for `requirements` parameter came via SDK, but documentation was missing. Fixes #3471
Successfully merging a pull request may close this issue.
See https://docs.databricks.com/en/libraries/workspace-files-libraries.html
The
databricks_library
provider should have aworkspace
block taking apath
to the workspace file.This is particularly relevant given DBR15's ability to support
requirements.txt
filesSample syntax:
If no support is planned (or not planned for a while), the documentation should be updated to reflect this rather than the conspicuous absence.
(The same happens to be true for volume files, too, which could be repeated verbatim as above with a text replacement. https://docs.databricks.com/en/libraries/volume-libraries.html )
The text was updated successfully, but these errors were encountered: