-
Notifications
You must be signed in to change notification settings - Fork 14.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bring back broken "connection-type/hook-class-name" check #33662
Conversation
One more fix to the provider.yaml pre-commit. It also missed the "hook-class-names" verification. This is why PinotHook has not been detected - this PR will only succeed after #33601 is merged. (But I wanted to add it now to have a proof that it would have detected it). |
Why? |
Continuation of apache#33640 - there were one more wrong check in the provider, that missed "hook-class-names" check
c7fc828
to
b66a3eb
Compare
This is a much better title to not confuse it with the removed "hook-class-names" entry. |
This one completes review and check of provider.yaml verifications. There was one more check - for duplicates - that did not work as expected. It was hiding errors detected. This PR fixes it and also adds a bit more diagnostics messagese on what is actually being checked to give a bit more clue if some check is not doing what it is supposed to be doing. Follow up after apache#33662 and apache#33640
This one completes review and check of provider.yaml verifications. There was one more check - for duplicates - that did not work as expected. It was hiding errors detected. This PR fixes it and also adds a bit more diagnostics messagese on what is actually being checked to give a bit more clue if some check is not doing what it is supposed to be doing. Follow up after #33662 and #33640
Continuation of #33640 - there were one more wrong check in the provider, that missed "hook-class-names" check
^ 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.