You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Kamil Bregula (JIRA)" <ji...@apache.org> on 2019/01/12 19:07:00 UTC

[jira] [Commented] (AIRFLOW-3684) Update bundled plugins to work with FAB-based UI

    [ https://issues.apache.org/jira/browse/AIRFLOW-3684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741368#comment-16741368 ] 

Kamil Bregula commented on AIRFLOW-3684:
----------------------------------------

Why is the plugin located in this repository? Maybe it's worth moving it to another project? You would not have to worry about its maintenance. Now this plug-in does not even have documentation. I suspect that nobody remembers it.

> Update bundled plugins to work with FAB-based UI
> ------------------------------------------------
>
>                 Key: AIRFLOW-3684
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3684
>             Project: Apache Airflow
>          Issue Type: Bug
>            Reporter: Ash Berlin-Taylor
>            Priority: Blocker
>             Fix For: 2.0.0
>
>
> We have one plugin in-tree (airflow.contrib.plugins.metastore_browser.main) that has a flask_blueprint - with the deprecation of the old UI in AIRFLOW-3303 this won't work anymore, so we should update that plugin.
> It might also be worth issuing a warning if a plugin has a {{admin_views}} attribute and no {{appbuilder_views}} (allow both to let a plugin support old and new Airflows.)
> We possibly need to update the plugin integration in the FAB-app to still support flask_blueprints (To support things that aren't views, such as static files).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)