-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Clean up remaining getattr connection DbApiHook #40665
Clean up remaining getattr connection DbApiHook #40665
Conversation
…n get_conn_id method from DbApiHook
…s using the new get_conn_id method of the DbApiHook
…on conn_name_attr
The pre-commit needs to be run as suggested in the error message :) |
…ate of minimal apache-airflow-providers-common-sql version
I get follow error stating that I need to regenerate the provider constraints, but when I run the follow command in breeze nothing is changed: breeze static-checks --type update-providers-dependencies --all-files Also my branch is up-to-date with gitbuh. |
Can you rebase it please @dabla ? I believe a conflicting change was merged soon after you pushed the PR and that's the root cause (currentlly you cannot even rebase it with the UI as it have conflicting changes (on dependencies update). |
--------- Co-authored-by: David Blain <david.blain@infrabel.be> Co-authored-by: David Blain <david.blain@b-holding.be>
This pull request also applies the cleanup done in the DbApiHook throughout all depending hooks regarding the duplicated calls using the getattr on the conn_name_attr. This was already done within the DbApiHook itself in the fix for PR 40615. The only drawback of this change is that all providers then need to update the min required version of the common.sql provider to be at the latest 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.