You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "Nathaniel Ritholtz (Jira)" <ji...@apache.org> on 2019/08/28 17:20:00 UTC
[jira] [Assigned] (AIRFLOW-5336) Add ability to make updating perms
on webserver init optional
[ https://issues.apache.org/jira/browse/AIRFLOW-5336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathaniel Ritholtz reassigned AIRFLOW-5336:
-------------------------------------------
Assignee: (was: Nathaniel Ritholtz)
> Add ability to make updating perms on webserver init optional
> -------------------------------------------------------------
>
> Key: AIRFLOW-5336
> URL: https://issues.apache.org/jira/browse/AIRFLOW-5336
> Project: Apache Airflow
> Issue Type: Improvement
> Components: webserver
> Affects Versions: 1.10.4
> Reporter: Nathaniel Ritholtz
> Priority: Minor
>
> Add ability to make updating perms on webserver init optional based off of 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.2#803003)