ashb opened a new issue #9506:
URL: https://github.com/apache/airflow/issues/9506
In Airflow 2.0 we should remove the ability to import hooks via the plugin
mechanism.
I think we should deprecate adding Operators and Hooks via the Airflow
plugin mechanism.
Similar to #9500, but this time for Hooks. (Separate PR as this time we want
to keep the ability to register hooks, but for operators even registering
should go.)
```
from airflow.hooks.my_plugin import MyHook
```
can become
```
from my_plugin import MyHook
```
with no impact on functionality/user code.
There is still a possible reason to "register" Hooks in a plugin -- namely
making the connection types available in the Connections screen. (We don't do
that currently, but we should, so keeping the ability to make
Discussed on mailing list here
https://lists.apache.org/thread.html/a1453d6a6f113709386b61c68c3f5cd61b258fe78f07811169500fe3%40%3Cdev.airflow.apache.org%3E
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
