mjpieters opened a new issue #9185:
URL: https://github.com/apache/airflow/issues/9185
**Description**
Please include plug-in information (see below) in the Airflow "About ->
Version" information page in the web interface.
**Use case / motivation**
Plug-ins have a lot of leeway in Airflow, adding not only operators,
sensors, hooks, and executors, but can also provide menu items and other, less
visible extensions to the Airflow server. However, you currently can't get an
overview of what plug-ins were loaded, or where they came from (some
information is logged at DEBUG level but is incomplete).
This makes verifying plug-in operation needlessly complicated.
Plug-ins are loaded from two locations:
- `.py` files in the directory named by `core.plugins_folder`
- entry points in any setuptools-installed Python project
Per plug-in, ideally the 'versions' page (or a similar page dedicated to
plugins) would list:
- plugin name
- source (plugins folder or entry point)
- for plugins folder plugins
- path relative to the plugins folder
- for entry point plugins
- the project name and version from the `EntryPoint.dist` object (using
`str(entry_point.dist)` should suffice)
- the entrypoint name, module and attributes information
(`str(entry_point)` provides this, already formatted).
- **NOT** the file location, that'd be a security issue. The entrypoint
information is enough to locate the plugin when someone has access to the
machine and the Python installation that runs Airflow.
- Optionally: information on the specific extension points provided by the
plug-in.
----------------------------------------------------------------
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]
