-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Remove the ability to add hooks to airflow.hooks namespace #12108
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
Remove the ability to add hooks to airflow.hooks namespace #12108
Conversation
|
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Backport packages$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*. |
| "import_errors", | ||
| "hooks_modules", | ||
| "macros_modules", | ||
| "executors_modules", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we remove executors in a different PR?
|
The PR needs to run all tests because it modifies core of Airflow! Please rebase it to latest master or ask committer to re-run it! |
Hooks do not need to live under "airflow.hooks" namespace for them to work -- so remove the ability to create them under there in plugins. Using them as normal python imports is good enough! We still allow them to be "registered" to support dynamically populating the connections list in the UI (which won't be done for 2.0) Closes apache#9507
312a216 to
6b5fee4
Compare
|
Deprecation warning for this added in #12133 |
We had deprecated & removed support for Sensors & Operators via Plugin for Airflow 2 in Jun 25, 2020 :) PRs: - apache#12108 - apache#9507
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As per my understand we don't use that code and instead use `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As per my understand we don't use that code and instead use `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As per my understand we don't use that code and instead use `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers. # Conflicts: # tests/plugins/test_plugin.py
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had removed registering hooks via plugin in #12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had deprecated & removed support for Sensors & Operators via Plugin for Airflow 2 in Jun 25, 2020 :) PRs: - apache#12108 - apache#9507
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had deprecated & removed support for Sensors & Operators via Plugin for Airflow 2 in Jun 25, 2020 :) PRs: - apache#12108 - apache#9507
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had deprecated & removed support for Sensors & Operators via Plugin for Airflow 2 in Jun 25, 2020 :) PRs: - apache#12108 - apache#9507
We had removed registering hooks via plugin in apache#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers.
We had deprecated & removed support for Sensors & Operators via Plugin for Airflow 2 in Jun 25, 2020 :) PRs: - apache/airflow#12108 - apache/airflow#9507 GitOrigin-RevId: 5c683fb60a9f794a113e8d95d88d84fe3c878267
We had removed registering hooks via plugin in apache/airflow#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers. GitOrigin-RevId: 2bf3af0a65631bb6b9271fca8a0c6724c996393c
We had deprecated & removed support for Sensors & Operators via Plugin for Airflow 2 in Jun 25, 2020 :) PRs: - apache/airflow#12108 - apache/airflow#9507 GitOrigin-RevId: 5c683fb60a9f794a113e8d95d88d84fe3c878267
We had removed registering hooks via plugin in apache/airflow#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers. GitOrigin-RevId: 2bf3af0a65631bb6b9271fca8a0c6724c996393c
We had deprecated & removed support for Sensors & Operators via Plugin for Airflow 2 in Jun 25, 2020 :) PRs: - apache/airflow#12108 - apache/airflow#9507 GitOrigin-RevId: 5c683fb60a9f794a113e8d95d88d84fe3c878267
We had removed registering hooks via plugin in apache/airflow#12108 for Airflow 2.0. We kept it for registering Connection form. As I understand it, we don't use that code but `ProvidersManager` (`airflow/providers_manager.py`) to register Connections from providers. GitOrigin-RevId: 2bf3af0a65631bb6b9271fca8a0c6724c996393c
Hooks do not need to live under "airflow.hooks" namespace for them to
work -- so remove the ability to create them under there in plugins.
Using them as normal python imports is good enough!
We still allow them to be "registered" to support dynamically populating
the connections list in the UI (which won't be done for 2.0)
Closes #9507
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.