[ https://issues.apache.org/jira/browse/AIRFLOW-2278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16425127#comment-16425127 ]
Mykola Mykhalov edited comment on AIRFLOW-2278 at 4/4/18 7:30 AM: ------------------------------------------------------------------ [~johnarnold] It uses natural way of DAGs refresh after editing, so it works with remote executors and separated services on different hosts. Just to be sure for 100%, I've tested it on cluster where we use Celery Executor and couple of servers. was (Author: miho): It uses natural way of DAGs refresh after editing, so it works with remote executors and separated services on different hosts. Just to be sure for 100%, I've tested it on cluster where we use Celery Executor and couple of servers. > Add possibility to edit DAGs in webapp > -------------------------------------- > > Key: AIRFLOW-2278 > URL: https://issues.apache.org/jira/browse/AIRFLOW-2278 > Project: Apache Airflow > Issue Type: Improvement > Components: webapp > Reporter: Mykola Mykhalov > Assignee: Mykola Mykhalov > Priority: Minor > > When you need to make some minor changes in your DAG would be nice to have > possibility to edit it from webapp. > To protect DAG from editing by everyone should be set up arg inside DAG > 'editable_by'. Where '*' means everyone, and ['user1', 'user2'] means > specific users. > Example when DAG can be editable in webapp by user1 and user2 only: > args = { > 'owner': 'airflow', > 'editable_by': ['user1', 'user2'], > 'start_date': airflow.utils.dates.days_ago(2) > } -- This message was sent by Atlassian JIRA (v7.6.3#76005)