Skip to content

Runtime authentication uses host = None in job clusters #202

@mgyucht

Description

@mgyucht

Seems like in an interactive cluster it will set the host correctly and get a bearer token all transparently as expected. For some reason the host is not set when running the same notebook in a job cluster, causing all attempts to use the WorkspaceClient with the host set to https://none/. Same user for both the interactive and job clusters and both running 12.2LTS.

I've also tried directly setting host=https:... in the WorkspaceClient() initialisation but the runtime auth seems to ignore that.

Job Cluster Bad
Interactive_Cluster_Good
Job_Cluster_Explicit_Hostname_Bad

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions