[GitHub] drewsonne opened a new pull request #4412: Load plugins from entry_points

[GitBox <gi...@apache.org>]

drewsonne opened a new pull request #4412: Load plugins from entry_points
URL: https://github.com/apache/incubator-airflow/pull/4412
 
 
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
   
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI changes:
   
   Added logic to load AirflowPlugins from the [entry_points](https://setuptools.readthedocs.io/en/latest/pkg_resources.html#id16). Rather than moving files on the OS, this allows plugins to be installed and distributed via `pip`. 
   
   Also added a callback to execute business logic from the plugin when the 
   
   ### Tests
   
   - [x] My PR adds the following unit tests:
    - `plugins_manager.PluginsEntrypointLoad`
    - `plugins_manager.PluginsTestValidator`
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [?] In case of new functionality, my PR adds documentation that describes how to use it.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
   
   I haven't written the documentation yet, as I wanted to see if there was an appetite for this kind of loading of plugins.
   
   ### Code Quality
   
   - [x] Passes `flake8`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services