You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Ash Berlin-Taylor (Jira)" <ji...@apache.org> on 2019/10/04 08:37:00 UTC
[jira] [Resolved] (AIRFLOW-2541) Ability to discover custom
plugins, operators, sensors, etc. from various locations
[ https://issues.apache.org/jira/browse/AIRFLOW-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ash Berlin-Taylor resolved AIRFLOW-2541.
----------------------------------------
Resolution: Done
It is now possible to add plugins to Airflow from python packages http://airflow.apache.org/plugins.html#plugins-as-python-packages so I think this meets your need.
If you would like to add multiple path support to plugins path anyway then you can re-open this Jira ticket and a PR is welcome. (If someone else wants to do this, comment and I can re-open the ticket for you.)
> Ability to discover custom plugins, operators, sensors, etc. from various locations
> -----------------------------------------------------------------------------------
>
> Key: AIRFLOW-2541
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2541
> Project: Apache Airflow
> Issue Type: Improvement
> Components: plugins
> Reporter: Ritesh Shrivastav
> Assignee: Ritesh Shrivastav
> Priority: Minor
> Labels: newbie, patch-available
> Attachments: plugin_manager.diff
>
>
> Provision to create custom plugins without dropping them into `$AIRFLOW_HOME/plugins` (or the directory defined in `airflow.cfg`).
> We can define one location in `airflow.cfg` but if we have multiple projects which will have their own workflows so, it would be ideal to implement custom plugins (along with operators, sensors, etc.) in those repositories itself and let them get discovered from there.
>
> A simple patch in attachment seems to solve this issue.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)