Skip to content

Azure connections extra fields are inconsistent between the doc, tests and the UI connections #30557

@hussein-awala

Description

@hussein-awala

Apache Airflow Provider(s)

microsoft-azure

Versions of Apache Airflow Providers

No response

Apache Airflow version

2.5.3

Operating System

Azure connections extra fields are inconsistent between the doc, tests and the UI connections

Deployment

Official Apache Airflow Helm Chart

Deployment details

No response

What happened

When creating an Azure connection from the UI, the extra fields are prefixed with extra__azure__, which is not used in the unit tests and not mentioned in the provider documentation.

In some of the hook/operators methods, we double read the field with and without extra__azure__ to support the connections created from the CLI (or via env vars) and the connections created from the webserver UI, but this double read is missing in some methods (ex #30556).

To fix this, we should fix the UI fields name and deprecate the fields with extra__azure__ in order to remove them in the future.

What you think should happen instead

No response

How to reproduce

~

Anything else

This should be a Task issue but it is reserved for maintainers.

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

Labels

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