-
Notifications
You must be signed in to change notification settings - Fork 17
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
[BUG] metadata-service auth type returns empty token #916
Comments
Hi @ericfeunekes. This error should only be affecting local notebooks. Can you confirm that other parts of the extension are affected as well? (eg running a python file) |
Yes that seems to be true. I don't really have a python file to run that way, but I do know it can connect to and show clusters, sync files, etc. |
I have the same issue. Is there any way to inspect this error in more detail? Otherwise, how to solve this namespace issue? |
This also affects the cli though. Recently I used the vs code extension and then opened a new terminal outside of vs code (in iterm2). When I tried using the cli it gave me the same error. It seems like the extension is setting a global environment variable that needs to be unset for the cli to work. This makes the extension break more than it helps. |
I have a similar problem. The extension takes over my databricks CLI. In stead of using the profile in my .databrickscfg or the configurations in my databricks.yml, it sets thing up with a default cluster (that I specified in the extension) and uses metadata-service as authentication method instead of azure cli. |
Experiencing the same. Kindly suggest a workaround for this. |
I was able to work around this issue by updating the |
Describe the bug
Once I connect to the Databricks server from the VS Code extention, it adds
.databricks/databricks.env
that includes a variableDATABRICKS_AUTH_TYPE=metadata-service
. I think this causes problems with authentication because I get the following error in the VS Code output window:create_and_register_databricks_globals - ValueError: default auth: metadata-service: Metadata Service returned empty token. Config: host=https://"https://***.azuredatabricks.net/", auth_type=metadata-service, cluster_id=***, metadata_service_url=***. Env: DATABRICKS_HOST, DATABRICKS_AUTH_TYPE, DATABRICKS_CLUSTER_ID, DATABRICKS_METADATA_SERVICE_URL
To Reproduce
Steps to reproduce the behavior:
System information:
Help: About
command (CMD-Shift-P).1.2.2
The text was updated successfully, but these errors were encountered: