Summary
On macOS, ucode's automatic Databricks CLI bootstrap runs brew install databricks. The Databricks CLI is not published to homebrew-core under that name — it lives in the databricks/tap Homebrew tap. As a result, brew install databricks resolves to an unrelated formula and installs the wrong tool (it resolves to DataGrip), leaving databricks still missing from PATH.
Where
src/ucode/databricks.py, in _run_databricks_cli_installer:
elif system == "Darwin" and shutil.which("brew"):
run(["brew", brew_subcommand, "databricks"], timeout=240)
This is reached from both install_databricks_cli() (fresh install) and ensure_databricks_cli_version() (auto-upgrade).
Expected
The installer should tap databricks/tap before installing, per the official install instructions:
brew tap databricks/tap
brew install databricks
Actual
brew install databricks installs the wrong package; the Databricks CLI is never installed, so subsequent databricks invocations fail.
Fix
Run brew tap databricks/tap before the install/upgrade on the Homebrew path. PR to follow.
Summary
On macOS, ucode's automatic Databricks CLI bootstrap runs
brew install databricks. The Databricks CLI is not published to homebrew-core under that name — it lives in thedatabricks/tapHomebrew tap. As a result,brew install databricksresolves to an unrelated formula and installs the wrong tool (it resolves to DataGrip), leavingdatabricksstill missing from PATH.Where
src/ucode/databricks.py, in_run_databricks_cli_installer:This is reached from both
install_databricks_cli()(fresh install) andensure_databricks_cli_version()(auto-upgrade).Expected
The installer should tap
databricks/tapbefore installing, per the official install instructions:Actual
brew install databricksinstalls the wrong package; the Databricks CLI is never installed, so subsequentdatabricksinvocations fail.Fix
Run
brew tap databricks/tapbefore the install/upgrade on the Homebrew path. PR to follow.