Add azure, google, authentication library limits to eager upgrade #27535
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When generating constraints for released providers we hit the same
pip
resolver backtracking issue - where it took very, very long time to resolve the dependencies for installing released providers on latest airflow from sources.In #27531 we've added limits to provider.yaml but currently released providers do not have those limits, so until we release them, we should add the limits to "eager upgrade dependencies" in our CI image - to help
pip
to figure out the right set of dependencies much faster.Also fixed a problem with extra "." in adal specification (seems it's
been ignored by
pip
anyway)^ 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.