[
https://issues.apache.org/jira/browse/AIRFLOW-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448062#comment-16448062
]
ASF subversion and git services commented on AIRFLOW-1433:
----------------------------------------------------------
Commit 6da88bb4206fbb52b2bcb592a1826faf8860738d in incubator-airflow's branch
refs/heads/master from [~wrp]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=6da88bb ]
[AIRFLOW-1433] Set default rbac to initdb
05e1861e24de42f9a2c649cd93041c5c744504e1 breaks
the api for
any program directly importing airflow.utils.
This sets
a reasonable default.
Closes #3240 from wrp/initdb
> Convert Airflow to Use FAB Framework
> ------------------------------------
>
> Key: AIRFLOW-1433
> URL: https://issues.apache.org/jira/browse/AIRFLOW-1433
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Joy Gao
> Assignee: Joy Gao
> Priority: Major
>
> The authentication capabilities in the RBAC design proposal introduces a
> significant amount of work that is otherwise already built-in in existing
> frameworks.
> Per community discussion, Flask-AppBuilder (FAB) is the best fit for Airflow
> as a foundation to implementing RBAC. This will support integration with
> different authentication backends out-of-the-box, and generate permissions
> for views and ORM models that will simplify view-level and dag-level access
> control.
> This implies modifying the current flask views, and deprecating the current
> Flask-Admin in favor of FAB's crud.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
