Skip to content

Better error message where non-compatible providers are not excluded#30629

Merged
potiuk merged 1 commit intoapache:mainfrom
potiuk:fail-installation-with-conflict-if-there-is-one
Apr 13, 2023
Merged

Better error message where non-compatible providers are not excluded#30629
potiuk merged 1 commit intoapache:mainfrom
potiuk:fail-installation-with-conflict-if-there-is-one

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented Apr 13, 2023

When compatibility check is performed for old version of Airflow, we attempt to install all providers for the old version. However if one of the providers has >= limit on Airflow for newer version of Airflow, this installation lead to attempting to upgrade airflow rather than fail, which could lead to misleading errors.

This change adds "airflow==x.y.z" taken from --use-airflow-version flag to the pip install command, which should in this case fail with much more accurate message, that the provider conflicts with airflo version.


^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

When compatibility check is performed for old version of Airflow,
we attempt to install all providers for the old version. However if
one of the providers has >= limit on Airflow for newer version of
Airflow, this installation lead to attempting to upgrade airflow
rather than fail, which could lead to misleading errors.

This change adds "airflow==x.y.z" taken from --use-airflow-version
flag to the `pip install` command, which should in this case fail
with much more accurate message, that the provider conflicts with
airflo version.
@potiuk potiuk merged commit 916dd96 into apache:main Apr 13, 2023
@potiuk potiuk deleted the fail-installation-with-conflict-if-there-is-one branch April 13, 2023 17:14
wookiist pushed a commit to wookiist/airflow that referenced this pull request Apr 19, 2023
…pache#30629)

When compatibility check is performed for old version of Airflow,
we attempt to install all providers for the old version. However if
one of the providers has >= limit on Airflow for newer version of
Airflow, this installation lead to attempting to upgrade airflow
rather than fail, which could lead to misleading errors.

This change adds "airflow==x.y.z" taken from --use-airflow-version
flag to the `pip install` command, which should in this case fail
with much more accurate message, that the provider conflicts with
airflo version.
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

Comments