Dbx

Latest version: v0.8.19

Safety actively analyzes 682244 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 7 of 11

0.6.2

Not secure
- Fix auth ordering (now env-variables based auth has priority across any other auth methods)

0.6.1

Not secure
- Fix import issues in `dbx.api.storage` package

0.6.0

Not secure
Added

- Added dev container config for VSCode and GitHub CodeSpaces
- tests are now parallel (x2 less time spent per each CI pipeline launch)
- url-strip behaviour for old-format workspace host names (which was unsupported in Mlflow API and caused a lot of
hardly explainable errors)

Changed

- Docs fixed in terms of allowed versions
- Non-strict path adjustment policy has been deleted from code and docs
- Dropped support for environment variables in plain JSON/YAML files
- Refactored code for reading configurations
- Drop support for `ruamel.yaml` in favor of standard `pyyaml`
- All tests are now based on pytest
- Full support for env variables in Jinja-based deployment configs
- Documentation improvements for Jinja-based templates
- Now package builds are performed with `pip` by default

Fixed

- Parsing of `requirements.txt` has been improved to properly handle comments in requirements files
- Recognition of `--branch-name` argument for `dbx launch`
- Path resolution for Jinja2 templates

0.5.0

Not secure
Added

- YAML Example for deploying multi-task Python job
- YAML Example for deploying multi-task Scala job
- Support including jinja templates from subpaths of the current working directory
- Add `--path` and `--checkout` options to the `dbx init`
- Change the format of the `python_basic` to use pytest
- Add `sync repo` and `sync dbfs` commands for syncing local files to Databricks and watching for changes.

Changed

- Refactor the configuration code
- Refactor the JSON-related code

0.4.1

Not secure
Fixed

- Jinja2-based file recognition behaviour

0.4.0

Not secure
Added

- Documentation, examples and support for Jobs API 2.1
- Support for Jinja2-based templates inside deployment configuration
- Added new `--job` argument to deploy command for a single-job deploy and convenience

Fixed

- Issue with empty paths in non-strict path adjustment logic
- Issues with `--no-package` argument for multi-task jobs
- Issues with named properties propagation for Jobs API 2.1

Page 7 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.