Databricks cli api command is not able to "configure default credentials"

[AHJiapengZhang]

Describe the issue

I have my profile configured at ~/.databrickscfg and it works well on databricks bundle but not api.

My ~/.databrickscfg looks like this:

[DEFAULT]

[project-prd]
host = https://adb-.1.azuredatabricks.net
token = 

[project-preprd-acc]
host = https://adb-.1.azuredatabricks.net
token = xxx

[project-nonprd]
host = https://adb-.1.azuredatabricks.net
token = xxx

Steps to reproduce the behavior

Please list the steps required to reproduce the issue, for example:
1.Run databricks api get /api/2.0/clusters/list
2. Error: default auth: cannot configure default credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method

Expected Behavior

Clear and concise description of what should have happened

Actual Behavior

Clear and concise description of what actually happened

OS and CLI version

MacOS
Databricks cli version 0.215.0

Is this a regression?

Did this work in a previous version of the CLI? If so, which versions did you try?

Debug Logs

15:04:08 INFO start pid=37071 version=0.215.0 args="databricks, api, get, /api/2.0/clusters/list, --debug"
15:04:08 DEBUG /Users/xxx/.databrickscfg has no DEFAULT profile configured pid=37071 sdk=true
15:04:08 DEBUG failed during request visitor: default auth: cannot configure default credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method pid=37071 sdk=true
Error: default auth: cannot configure default credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method
15:04:08 ERROR failed execution pid=37071 exit_code=1 error="default auth: cannot configure default credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method"

[andrewnester]

@AHJiapengZhang are the hosts for all these profiles are the same? if not, which one do you have configured in bundles? Also, please try to use the latest CLI version (0.227.0) and run databricks auth describe command to help troubleshoot what is the error

[AHJiapengZhang]

@AHJiapengZhang are the hosts for all these profiles are the same? if not, which one do you have configured in bundles? Also, please try to use the latest CLI version (0.227.0) and run databricks auth describe command to help troubleshoot what is the error

@andrewnester
Hosts are different but I renamed them that way here. I upgraded to 0.227 and get this for databricks auth describe:

Unable to authenticate: please specify target
-----
Current configuration:

If I move out of the current folder(it contains serveral databricks bundle yamls), I will get :

Workspace profiles defined in ~/.databrickscfg
  project-prd (https://adb-1xxx.1.azuredatabricks.net)
  project-preprd
  project-preprd-acc
  project-nonprd

and the result for : databricks api get /api/2.0/clusters/list is:

Error: failed during request visitor: default auth: cannot configure default credentials, please check https://docs.databricks.com/en/dev-tools/auth.html#databricks-client-unified-authentication to configure credentials for your preferred authentication method

[andrewnester]

So the first error relates to this issue and we're working on it #1358

The last one seems to be related to the different way we handle auth for API command group.

Just to confirm, does databricks current-user me works correctly for you?

[AHJiapengZhang]

databricks current-user me

@andrewnester Same as databricks auth describe if it's inside project folder it will say please specify target if outside of folder it display the same workspace profiles to choose from

[andrewnester]

@AHJiapengZhang you have to choose a profile to use because there is no default profile configured in your databricks config. You then can use the same profile in your api commands by providing -p flag and profile name