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

ASF subversion and git services commented on AIRFLOW-5336:
----------------------------------------------------------

Commit 90705319817eb5f97a5b7d802e1c32f9fc45b373 in airflow's branch 
refs/heads/master from Nathaniel Ritholtz
[ https://gitbox.apache.org/repos/asf?p=airflow.git;h=9070531 ]

[AIRFLOW-5336] Add ability to make updating FAB perms on webserver in… (#5940)

Co-Authored-By: Kaxil Naik <[email protected]>


> 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)

Reply via email to