Skip to content

Conversation

@dstandish
Copy link
Contributor

From airflow version 2.3, extra prefixes are not required so we enable them here.

@potiuk
Copy link
Member

potiuk commented Oct 23, 2022

Needs conflict resolving :(

From airflow version 2.3, extra prefixes are not required so we enable them here.
@dstandish dstandish force-pushed the azure-data-factory-no-prefix branch from d9a989f to 255eb78 Compare October 24, 2022 02:56
@dstandish dstandish merged commit 6b9e76b into apache:main Oct 24, 2022
@dstandish dstandish deleted the azure-data-factory-no-prefix branch October 24, 2022 04:16
pankajkoti added a commit to astronomer/astronomer-providers that referenced this pull request Feb 27, 2023
…Azure ADF DAG failure (#899)

* Support retriveing extra fields which do not have extra prefix set

With the 5.0.0 release of the Microsoft Azure PR, the PR apache/airflow#27047
introduced a breaking change where while creating new connections,
the ``extra__`` prefix is no longer set for extra fields in the conneciton.
This issue was not identified with testing the 5.0.0 RC because, it
only happens for new connections that are created. The existing connections
still contain the extra fiels with the ``extra__`` prefix. Hence, the
existing code which looks for the connection field with the prefix
``extra__azure_data_factory__subscriptionId`` works on the older deployment
with the new provider release as the connection was created before the release,
but it fails on new deployments when a fresh connection is created.

To fix this, we're removing the prefix while retrieving the connection
field and at the same time we're supporting previously created connections
by using the same ``get_field`` method from Airflow OSS introduced
in the same PR above to allow backward compatibility.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants