This is an enhanced Databricks CLI that was created as a missing addition to Databricks CLI to manage it from the terminal or CI/CD pipeline.

It is designed to be used by humans to solve problems, not for problems to use humans.

For most commands you should prefer using standard CLI, this tool is only containing enhancements and missing parts.

Although it’s written in C# (mostly due to the fact that I already have databricks API exposed via stowage) it is a fully self-contained single-file executable for Linux, Windows and MacOSX.


Download from the releases section i.e. (replace version)

wget https://github.com/aloneguid/databricks-cli/releases/download/1.3.1/dbx-linux-x64.zip
unzip dbx-linux-x64.zip
./dbx ...


First, set DATABRICKS_HOST and DATABRICKS_TOKEN environment variables to your selected host. Those are standard variables that standard CLI requires. Optionally, if you have already installed the official databricks CLI, this tool will just read your preconfigured credentials.

Commands are self-explanatory and can be listed by launching dbx without parameters. Run appropriate executable (dbx on Linux or dbx.exe on Windows) .

Managing Queries (Databricks SQL)


dbx query list


Id Name
1 Query 1
2 Query 2
3 Query 3

Optionally, you can pas --format=JSON to almost any command, so it can be parsed with jq.

Take Ownership

dbx query takeover 1 me@domain.com

Takes over an ownership from current owner to me@domain.com for query 1 (raw id). This is useful when a person is not available and query needs to be edited/changed.

Managing Clusters


dbx cluster list


You can start/stop clusters by passing their id’s or name’s substring unlike official tooling that only allows IDs:

dbx cluster start <substring>
dbx cluster stop <substring>

Managing Jobs


dbx job list


You can start/stop jobs by passing their id’s or name’s substring unlike official tooling that only allows IDs:

dbx job start <substring>
dbx job stop <substring>

Upserting a Job

This allows to create or update a job by specifying job json file. It will try to find the job by name specified in the json file and update it, otherwise a new job is created. Official tooling requires you to know job id beforehand, check if it exists first, get the id, and then update. This is hairy and overcomplicated.

dbx job upsert <json file path>

Executing Code Remotely

dbx exec -h

Source available on GitHub.

this project is not affiliated with databrickslabs/dbx and name clash came as a surprise and total coincidence!

Thanks! You can always email me or use contact form for more questions/comments etc.