Split providers out of the main "airflow/" tree into a UV workspace project #42505
+716
−595
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.
As discussed https://lists.apache.org/thread/dyv5jhvt65xs6l5o2byc2b67f4wlwf6r, this is the first part of the new layout.
This is only a partial split so far. It moves all the code and tests, but the provider release generation code hasn't moved yet as it's a few weeks until the next batch, and I wan't to try and keep this already huge PR as small as possible. Likewise the creation of
core/
will be a follow on PRIn addition to the straight file rename the other changes I had to make here are:
Some mypy/typing fixes.
Mypy can be fragile about what it picks up when, so maybe some of those changes were caused by that. But the typing changes aren't large.
Improve typing in common.sql type stub
Again, likely a mypy file oddity, but the types should be safe
Removed the
check-providers-init-file-missing
checkThis isn't needed now that airflow/providers shouldn't exist at all in the main tree.
In future we should switch how the CI image is built to make better use of UV caching than our own approach as that would remvoe a lot of custom code.
^ 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.