Databricks CLI

CLI discovered

Details

Command: databricks
Docs: https://docs.databricks.com/aws/en/dev-tools/cli/

Authentication

Databricks user OAuth app/client oauth2 discovered Set up OAuth ↗

$ databricks auth login

For user-authorized integrations, use Databricks OAuth as described in Authorize user access to Databricks with OAuth. For interactive tools, Databricks recommends unified authentication; for custom apps you can follow the manual OAuth flow on that page. For account-level operations set DATABRICKS_HOST to https://accounts.cloud.databricks.com; for workspace APIs set it to your workspace URL.

Databricks service principal OAuth client credentials oauth2_cc discovered Set up OAuth ↗

env DATABRICKS_HOST, DATABRICKS_CLIENT_ID, DATABRICKS_CLIENT_SECRET

Create a Databricks service principal and then create an OAuth secret as described in Authorize service principal access to Databricks with OAuth. Databricks recommends unified authentication for tools/SDKs; for custom integrations you can use the manual M2M token flow from that page. For account-level operations use DATABRICKS_HOST = https://accounts.cloud.databricks.com; for workspace APIs use your workspace URL.

Databricks personal access token (workspace-level legacy token) bearer discovered Get token ↗

env DATABRICKS_HOST, DATABRICKS_TOKEN

In your Databricks workspace, open Settings → Developer → Access tokens → Manage → Generate new token as documented in Personal access tokens (legacy). PATs are workspace-scoped and cannot be used for account-level APIs.