Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

DATABRICKS_HOST env variable is ignored when using CLI inside DAB directory

Offen
  • Stimmt etwas nicht?
#4,502 2 Kommentare 2 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

@simonfaltum arbeitet bereits daran.

Seit 23.2.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

auth Bug CLI No Autoclose
Describe the issue

When executing non-bundle commands (e.g., databricks current-user me) from within a directory containing a Databricks Asset Bundle (databricks.yml file exists), the CLI uses the bundle's default target of databricks.yml file over the explicitly defined DATABRICKS_HOST environment variable. That should never be used as we are running a non-bundle command.

Behavior:

  • Non-DAB commands inside DAB folder: The CLI ignores DATABRICKS_HOST and attempts to connect to the default target defined in databricks.yml.
  • Non-DAB commands outside DAB folder: The CLI correctly uses DATABRICKS_HOST.
  • DAB commands: Correctly respects DATABRICKS_HOST defined.
Steps to reproduce the behavior
  1. Create a databricks.yml file in the current directory with a dev target set as default:
targets:
  dev:
    mode: development
    default: true
    workspace:
      host: https://dev-environment.cloud.databricks.com
  stg:
    mode: production
    workspace:
      host: https://stg-environment.cloud.databricks.com
  1. Set environment variables to point to a different environment (Staging):
export DATABRICKS_HOST=https://stg-environment.cloud.databricks.com
export DATABRICKS_TOKEN=dapi_stg_token_here
  1. Execute a non-bundle command with debug logging in DAB folder (where databricks.yml file exists):
databricks current-user me --debug
Expected Behavior

The CLI should use the environment variable DATABRICKS_HOST. The command should execute against the Staging environment.

Actual Behavior

The CLI detects the bundle, loads the dev target because it is marked as default: true, and attempts to authenticate against the Dev environment, resulting in an Invalid Token error (as the token provided is for Staging).

OS and CLI version
  • OS: Linux (Docker python:3.11-alpine)
  • Databricks CLI Version: v0.288.0
Is this a regression?

Unknown, but consistently reproducible since at least v0.283.0.

Debug Logs

The logs clearly show the SelectDefaultTarget mutator forcing the target to dev despite the environment variables:

$ cd databricks
$ databricks current-user me --debug
15:35:06 Info: start pid=44 version=0.288.0 args="databricks, current-user, me, --debug"
15:35:06 Debug: Found bundle root at /my_repo_root/databricks (file /my_repo_root/databricks/databricks.yml) pid=44
15:35:06 Info: Phase: load pid=44
15:35:06 Debug: Apply pid=44 mutator=EntryPoint
15:35:06 Debug: Apply pid=44 mutator=scripts.preinit
15:35:06 Debug: No script defined for preinit, skipping pid=44 mutator=scripts.preinit
15:35:06 Debug: Apply pid=44 mutator=ProcessRootIncludes
15:35:06 Debug: Apply pid=44 mutator=ProcessRootIncludes mutator=ProcessInclude(resources/my_job_a.job.yml)
15:35:06 Debug: Apply pid=44 mutator=ProcessRootIncludes mutator=ProcessInclude(resources/my_job_b.job.yml)
15:35:06 Debug: Apply pid=44 mutator=VerifyCliVersion
15:35:06 Debug: Apply pid=44 mutator=EnvironmentsToTargets
15:35:06 Debug: Apply pid=44 mutator=ComputeIdToClusterId
15:35:06 Debug: Apply pid=44 mutator=InitializeVariables
15:35:06 Debug: Apply pid=44 mutator=DefineDefaultTarget(default)
15:35:06 Debug: Apply pid=44 mutator=validate:unique_resource_keys
15:35:06 Debug: Apply pid=44 mutator=SelectDefaultTarget
15:35:06 Debug: Apply pid=44 mutator=SelectDefaultTarget mutator=SelectTarget(dev)
15:35:06 Debug: GET /api/2.0/preview/scim/v2/Me
< HTTP/2.0 400 Bad Request
< Invalid Token pid=44 sdk=true
15:35:06 Debug: non-retriable error: Invalid Token pid=44 sdk=true
Error: Invalid Token
15:35:06 Info: failed execution pid=44 exit_code=1 error="Invalid Token"
15:35:06 Debug: no telemetry logs to upload pid=44
Vorherrschende Sprache
Go
Sterne
396
Forks
233
Ø Merge
1 T. 12 Std.
Gemergte PRs (30 T.)
283

Entwicklungsumgebung

Die Einrichtungsdateien dieses Projekts haben wir noch nicht geprüft. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus databricks/cli

Alle Issues in databricks/cli

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.