-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Login loop when using databricks account with azure service principle #726
Comments
Thanks for reporting. We'll investigate and post back here. |
There's a couple of underlying issues to be addressed, but you can unblock yourself by adding |
github-merge-queue bot
pushed a commit
that referenced
this issue
Sep 11, 2023
## Changes The previous implementation ran the risk of infinite looping for the account client due to a mismatch in determining what constitutes an account client between the CLI and SDK (see [here](https://github.com/databricks/cli/blob/83443bae8d8ad4df3758f4192c6bbe613faae9c4/libs/databrickscfg/profiles.go#L61) and [here](https://github.com/databricks/databricks-sdk-go/blob/0fdc5165e57a4e7af6ec97b47595c6dddf37b10b/config/config.go#L160)). Ultimately, this code must never infinite loop. If a user is prompted and selects a profile that cannot be used, they should receive that feedback immediately and try again, instead of being prompted again. Related to #726. ## Tests <!-- How is this tested? -->
@BramWeterings Note that without specifying the Thanks again for reporting this issue! |
hectorcast-db
pushed a commit
that referenced
this issue
Oct 13, 2023
## Changes The previous implementation ran the risk of infinite looping for the account client due to a mismatch in determining what constitutes an account client between the CLI and SDK (see [here](https://github.com/databricks/cli/blob/83443bae8d8ad4df3758f4192c6bbe613faae9c4/libs/databrickscfg/profiles.go#L61) and [here](https://github.com/databricks/databricks-sdk-go/blob/0fdc5165e57a4e7af6ec97b47595c6dddf37b10b/config/config.go#L160)). Ultimately, this code must never infinite loop. If a user is prompted and selects a profile that cannot be used, they should receive that feedback immediately and try again, instead of being prompted again. Related to #726. ## Tests <!-- How is this tested? -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm trying to connect a workspace to a metastore. Connecting on the account level does not seem to work:
Profile is configured as
When i run the command
databricks account metastore-assignments create $WorkspaceID $MetastoreID
nothing is returned, it just waits.
when i run it with --debug-level trace it seems to be stuck in a loop
Loging in with the used credentials works fine, i validated that the SP has the admin role on account level
running databricks cli version v0.203.3
The text was updated successfully, but these errors were encountered: