Dbx

Latest version: v0.8.18

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

Scan your dependencies

Page 5 of 11

0.7.1

Not secure
Added

- ⚡️`dbx destroy` command
- ☁️ failsafe behaviour for shared clusters when assets-based launch is used
- 📖 Documentation with cluster types guidance
- 📖 Documentation with scheduling and orchestration links
- 📖 Documentation for mixed-mode projects DevOps

Changed

- ✨Add `.dbx/sync` folder to template gitignore
- ✨Changed the dependencies from the `mlflow` to a more lightweight `mlflow-skinny` option
- ✨Added suppression for too verbose `click` stacktraces
- ⚡️added `execute_shell_command` fixture, improving tests performance x2
- ⚡️added failsafe check for `get_experiment_by_name` call

0.7.0

Not secure
Added

- 🎨Switch all the CLI interfaces to `typer`
- ✨Add `workflow-name` argument to `dbx deploy`, `dbx launch` and `dbx execute`
- ✨Add `--workflows` argument to `dbx deploy`
- ✨Add `--assets-only` and `--from-assets` as a clearer replacement for old arguments
- ⚡️Add support for `--environment` parameter for `dbx sync` commands
- ✨Add flexible parameter overriding logic for `dbx execute` via new `--parameters` option
- ✨Add flexible parameter overriding logic for `dbx launch` via new `--parameters` option (RunNow API)
- ✨Add flexible parameter overriding logic for `dbx launch` via new `--parameters` option (RunSubmit API)
- ✨Add inplace Jinja support for YAML and JSON files, can be configured
via `dbx configure --enable-inplace-jinja-support`
- ✨Add build logic options for `pip`, `poetry` and `flit`
- ✨Add build logic customization with `build.commands` section
- ✨Add support for custom Python functions in Jinja templates

Changed

- ✨Arguments `--allow-delete-unmatched`/`--disallow-delete-unmatched` were **replaced** with `--unmatched-behaviour`
option.
- 🏷️Deprecate `jobs` section and rename it to `workflows`
- 🏷️Deprecate `job` and `jobs` options and rename it to `workflow` argument
- ✨Refactored all cluster-relevant methods into a separate `ClusterController`
- ✨Refactored model-related components for `.dbx/project.json` file
- ✨Refactored `launch`-related API-level code
- ⚡️Deleted `autouse` of `temp_project` fixture to speedup the tests
- 🚩Deprecate `--files-only` and `--as-run-submit` options
- 🚩Deprecate `--files-only` and `--as-run-submit` options
- 🚩Delete the Azure Data Factory-related functionality.
Unfortunately we're unable to make this integration stable and secure due to resource lack and lack of RunNow API.
- 💎Documentation framework changed from `sphinx` to `mkdocs`
- 💎Documentation has been heavily re-worked and improved

Fixed

- 🐛`dbx sync` now takes into account `HTTP(S)_PROXY` env variables
- 🐛empty task parameters are now supported
- 🐛ACLs are now properly updated for Jobs API 2.1

0.6.12

Not secure
Added

- `--jinja-variables-file` for `dbx execute`

Fixed

- Support `jobs_api_version` values provided by config in `ApiClient` construction
- References and wording in the Python template

0.6.11

Not secure
Fixed

- Callback issue in `--jinja-variables-file` for `dbx deploy`

0.6.10

Not secure
Added

- Added support for `python_wheel_task` in `dbx execute`

Fixed

- Error in case when `.dbx/project.json` is non-existent
- Error in case when `environment` is not provided in the project file
- Path usage when `--upload-via-context` on win platform

0.6.9

Not secure
Added

- Additional `sync` command options (`--no-use-gitignore`, `--force-include`, etc.) for more control over what is
synced.
- Additional `init` command option `--template` was added to allow using dbx templates distributed as part of python
packages.
- Refactored the `--deployment-file` option for better modularity of the code
- Add upload via context for `dbx execute`

Page 5 of 11

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.