mirror of https://github.com/databricks/cli.git
d525ff67be
Bumps [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv) from 4 to 5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/astral-sh/setup-uv/releases">astral-sh/setup-uv's releases</a>.</em></p> <blockquote> <h2>v5.0.0 🎄 Merry Christmas - Help fastly and users by default</h2> <h2>Changes</h2> <p>This christmans 🎄 release is a bit early bit still full of presents 🎁 Since we are changing some of the defaults this can lead to breaking changes, thus the major version increase.</p> <p>Here are the highlights:</p> <h3><a href="https://redirect.github.com/astral-sh/setup-uv/pull/193">Default to enable-cache: true on GitHub hosted runners</a></h3> <p>Did you know that that Fastly, the company hosting PyPI, theoretically has to pay $12.5 million per month and so far have served more than 2.41 <strong>exabytes</strong> of data? <img src="https://github.com/user-attachments/assets/f2f6cb3f-68f6-4e37-abb1-d3bf1f278533" alt="image" /></p> <p>This is why <a href="https://redirect.github.com/astral-sh/setup-uv/issues/54">they asked us</a> to turn on caching by default. After weighting the pros and cons we decided to automatically upload the cache to the GitHub Actions cache when running on GitHub hosted runners. You can still disable that with <code>enable-cache: false</code>.</p> <p>I remember when I first got into actions and didn't understand all the magic. I was baffled that some actions did something behind the scenes to make everything faster. I hope with this change we help a lot of users who are don't want to or are afraid to understand what <code>enable-cache</code> does.</p> <h3><a href="https://redirect.github.com/astral-sh/setup-uv/pull/185">Add **/requirements*.txt to default cache-dependency-glob</a></h3> <p>If caching is enabled we automatically searched for a <code>uv.lock</code> file and when this changed we knew we had to refresh the cache. A lot of projects don't use this but rather the good old <code>requirements.txt</code>. We now automatically search for both <code>uv.lock</code>and <code>requirements*.txt</code> (this means also <code>requirements-test.txt</code>, <code>requirements-dev.txt</code>, ...) files. You can change this with <code>cache-dependency-glob</code></p> <h3><a href="https://redirect.github.com/astral-sh/setup-uv/pull/194">Auto activate venv when python-version is set</a></h3> <p>Some workflows install packages on the fly. This automatically works when using a python version that is already present on the runner. But if uv installs the version, e.g. because it is a free-threaded version or an old one, it is a <a href="https://astral.sh/blog/python-build-standalone">standalone-build</a> and installing packages "into the system" is not possible.</p> <p>We now automatically create a new virtual environment with <code>uv venv</code> and activate it for the rest of the workflow if <code>python-version</code> is used. This means you can now do</p> <pre lang="yaml"><code>- name: Install uv uses: astral-sh/setup-uv@auto-environment with: python-version: 3.13t - run: uv pip install -i https://pypi.anaconda.org/scientific-python-nightly-wheels/simple cython </code></pre> <h2>🚨 Breaking changes</h2> <ul> <li>Default to enable-cache: true on GitHub hosted runners <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/193">#193</a>)</li> <li>Add **/requirements*.txt to default cache-dependency-glob <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/185">#185</a>)</li> </ul> <h2>🐛 Bug fixes</h2> <ul> <li>Always use api.github.com <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/191">#191</a>)</li> </ul> <h2>🚀 Enhancements</h2> <ul> <li>Auto activate venv when python-version is set <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/194">#194</a>)</li> <li>Add python version to cache key <a href="https://github.com/eifinger"><code>@eifinger</code></a> (<a href="https://redirect.github.com/astral-sh/setup-uv/issues/187">#187</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href=" |
||
|---|---|---|
| .codegen | ||
| .github | ||
| .vscode | ||
| acceptance | ||
| bundle | ||
| cmd | ||
| docker | ||
| docs | ||
| integration | ||
| internal | ||
| libs | ||
| .codegen.json | ||
| .git-blame-ignore-revs | ||
| .gitattributes | ||
| .gitignore | ||
| .golangci.yaml | ||
| .goreleaser.yaml | ||
| .mockery.yaml | ||
| CHANGELOG.md | ||
| Dockerfile | ||
| LICENSE | ||
| Makefile | ||
| NOTICE | ||
| README.md | ||
| go.mod | ||
| go.sum | ||
| main.go | ||
| main_test.go | ||
README.md
Databricks CLI
This project is in Public Preview.
Documentation is available at https://docs.databricks.com/dev-tools/cli/databricks-cli.html.
Installation
This CLI is packaged as a dependency-free binary executable and may be located in any directory. See https://github.com/databricks/cli/releases for releases and the Databricks documentation for detailed information about installing the CLI.
Homebrew
We maintain a Homebrew tap for installing the Databricks CLI. You can find instructions for how to install, upgrade and downgrade the CLI using Homebrew here.
Docker
You can use the CLI via a Docker image by pulling the image from ghcr.io. You can find all available versions
at: https://github.com/databricks/cli/pkgs/container/cli.
docker pull ghcr.io/databricks/cli:latest
Example of how to run the CLI using the Docker image. More documentation is available at https://docs.databricks.com/dev-tools/bundles/airgapped-environment.html.
docker run -e DATABRICKS_HOST=$YOUR_HOST_URL -e DATABRICKS_TOKEN=$YOUR_TOKEN ghcr.io/databricks/cli:latest current-user me
Authentication
This CLI follows the Databricks Unified Authentication principles.
You can find a detailed description at https://github.com/databricks/databricks-sdk-go#authentication.
Privacy Notice
Databricks CLI use is subject to the Databricks License and Databricks Privacy Notice, including any Usage Data provisions.