Skip to content

databricks connect does not support specify a user managed identity while airflow run in Azure VM #65588

@sydongda

Description

@sydongda

Under which category would you file this issue?

Providers

Apache Airflow version

2.10.5

What happened and how to reproduce it?

Setup Airflow in Azure VM, and assigned a user managed identity, dag will connect to databricks as the user managed identity. However, current databricks provider does not support such a configuration like azure_managed_identity_client_id or something like this. only use_azure_managed_identity option support.

What you think should happen instead?

hope the connect support specify a user managed identity, instead use a default one.

Operating System

Ubuntu

Deployment

Virtualenv installation

Apache Airflow Provider(s)

databricks

Versions of Apache Airflow Providers

apache-airflow-providers-databricks==6.10.0

Official Helm Chart version

Not Applicable

Kubernetes Version

No response

Helm Chart configuration

No response

Docker Image customizations

No response

Anything else?

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions