You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the issue is
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
Configured databricks config file with host, client-id and client secret and created a non-prod profile, when trying to run databricks clusters list --profile non-prod
See error: default auth: oauth-m2m: oidc: databricks OAuth is not supported for this host. Config: host=https://adb-******************.azuredatabricks.net, profile=non-prod, client_id=**********, client_secret=, databricks_cli_path=C:\Users\36075\AppData\Local\Microsoft\WinGet\Packages\Databricks.DatabricksCLI_Microsoft.Winget.Source_8wekyb3d8bbwe\databricks.exe. Env: DATABRICKS_CONFIG_PROFILE, DATABRICKS_CLI_PATH
Expected Behavior
tried with other host and its working as expected
Actual Behavior
actually my use case is i use this profile for budle deploymenr
OS and CLI version
Please include the version of the CLI (eg: v0.1.2) and the operating system (eg: windows). You can run databricks --version to get the version of your Databricks CLI
Databricks CLI v0.236.0
Windows Machine
Is this a regression?
Did this work in a previous version of the CLI? If so, which versions did you try? didnr try
Debug Logs
Output logs if you run the command with debug logs enabled. Example: databricks clusters list --log-level=debug. Redact if needed
The text was updated successfully, but these errors were encountered:
Describe the issue
A clear and concise description of what the issue is
Steps to reproduce the behavior
Please list the steps required to reproduce the issue, for example:
Expected Behavior
tried with other host and its working as expected
Actual Behavior
actually my use case is i use this profile for budle deploymenr
OS and CLI version
Please include the version of the CLI (eg: v0.1.2) and the operating system (eg: windows). You can run databricks --version to get the version of your Databricks CLI
Databricks CLI v0.236.0
Windows Machine
Is this a regression?
Did this work in a previous version of the CLI? If so, which versions did you try? didnr try
Debug Logs
Output logs if you run the command with debug logs enabled. Example: databricks clusters list --log-level=debug. Redact if needed
The text was updated successfully, but these errors were encountered: