Databricks CLI auth login command removes cluster id

[frbaxter-kr]

Describe the issue

Starting with Databricks CLI v0.233.0, doing a "databricks auth login" removes data from my profile entry.

Steps to reproduce the behavior

My profile before: [test] cluster_id = 0816-163139-kqxcega3 host = https://adb-9999999999999999.1.azuredatabricks.net auth_type = databricks-cli

$ databricks auth login

My profile after: [test] host = https://adb-9999999999999999.1.azuredatabricks.net auth_type = databricks-cli

Expected Behavior

Doing a login should not delete profile information, it should only authenticate.

Actual Behavior

My profile was ruined.

OS and CLI version

Databricks CLI v0.233.0

Is this a regression?

Yes, all versions before this worked correctly.

Debug Logs

N/A

[github-actions[bot]]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.

[dabruehl]

I run into same issue today with Databricks CLI v0.248.0. Is there any fix or workaround for this?

I know there is a way with --configure-cluster. However, this prompts instead of just use what was defined in .databrickscfg cluster_id.

[dabruehl]

@andrewnester any update on this issue or workarounds?

[andrewnester]

@dabruehl have you tried to pass the cluster id as input for the command, something like this?

databricks auth login --host [email protected] --configure-cluster <<< "my_cluster_id"

[dabruehl]

@andrewnester thx for your input.

cluster ID does not work. It needs to be the cluster name in lower case (because of the search)

databricks auth login --host [email protected] --configure-cluster <<< "my_cluster_name_in_lower_case"

I still have the same questions as @frbaxter-kr. Why does login change the databrickscfg file? It just needs to login.

[magnussommarsjo]

Have the same issue. cluster_id is removed every time doing databricks auth login -p <profile>.

Databricks CLI v0.252.0

[frbaxter-kr]

We worked around this issue by writing a wrapper around the Databricks CLI. It's a shame they don't care about this bug, it's really confusing for our users. I also hate the INI file format when everybody else in the world is using yaml for configuration. The INI file format won't allow spaces or case sensitivity the way it has been implemented.

The Databricks CLI does a lot, but it's really clunky and could be so much better.