[
https://issues.apache.org/jira/browse/AIRFLOW-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16961423#comment-16961423
]
ASF subversion and git services commented on AIRFLOW-5336:
----------------------------------------------------------
Commit 53ae47f8e50de5cd22498b6cc0cc6a818aa68f8b in airflow's branch
refs/heads/v1-10-test from Nathaniel Ritholtz
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=53ae47f ]
[AIRFLOW-5336] Make updating FAB perms on webserver optional (#5940)
> Add ability to make updating FAB perms on webserver init optional
> -----------------------------------------------------------------
>
> Key: AIRFLOW-5336
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5336
> Project: Apache Airflow
> Issue Type: Bug
> Components: webserver
> Affects Versions: 1.10.4
> Reporter: Nathaniel Ritholtz
> Priority: Major
>
> Add ability to make updating perms and other syncs on webserver init optional
> similar to https://github.com/dpgaspar/Flask-AppBuilder/pull/625
> I am running into issues where multiple webserver processes are running what
> I believe is the sync_perm and it causes there to be records in the
> ab_permission_view with null permission_id (ultimately resulting in both
> processes crashing until I either manually clean them up or recreate the
> table). I envision being able to shut it off on the webserver init and use a
> one-off run that I am currently using, that handles it as part of deployment
> via the sync_perm CLI command.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
