Properly classify google_vendor package to google provider#30659
Merged
potiuk merged 1 commit intoApr 15, 2023
Conversation
We've recently added google_venor package to vendor-in ads library, and we had to do it outside of regular google provider package, because internally the library assumed our google package is top level package when discovering the right relative imports (apache#30544). This confused the pre-commit that updates provider depedencies to not recognise the package and print warnings about bad classification. Special case handling will classify it to google provider.
eladkal
approved these changes
Apr 15, 2023
hussein-awala
approved these changes
Apr 15, 2023
wookiist
pushed a commit
to wookiist/airflow
that referenced
this pull request
Apr 19, 2023
) We've recently added google_venor package to vendor-in ads library, and we had to do it outside of regular google provider package, because internally the library assumed our google package is top level package when discovering the right relative imports (apache#30544). This confused the pre-commit that updates provider depedencies to not recognise the package and print warnings about bad classification. Special case handling will classify it to google provider.
ephraimbuddy
added
the
changelog:skip
ephraimbuddy
pushed a commit
that referenced
this pull request
Apr 21, 2023
We've recently added google_venor package to vendor-in ads library, and we had to do it outside of regular google provider package, because internally the library assumed our google package is top level package when discovering the right relative imports (#30544). This confused the pre-commit that updates provider depedencies to not recognise the package and print warnings about bad classification. Special case handling will classify it to google provider. (cherry picked from commit d87eefc)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
We've recently added google_venor package to vendor-in ads library, and we had to do it outside of regular google provider package, because internally the library assumed our google package is top level package when discovering the right relative imports (#30544).
This confused the pre-commit that updates provider depedencies to not recognise the package and print warnings about bad classification.
Special case handling will classify it to google provider.
^ 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.rstor{issue_number}.significant.rst, in newsfragments.