eladkal edited a comment on issue #18410: URL: https://github.com/apache/airflow/issues/18410#issuecomment-933641048
@alex-astronomer I can argue that the DAGs should not be paused. As cluster admin I add/remove/update policies. I don't always know what DAGs are going to be effected by a policy I just add it and then all effected users change their code accordingly. If you prevent DAGs from running you have 2 edge cases: 1. If a policy is removed - who would know to set the DAG back to active? How will they be notified? 2. If a policy is changed (lets say first policy had a horrible exception message and the change made the message better) the user will never get the updated message because the DAG is in paused and can not run. I think the easiest way to overcome this is just having a configuration in airflow.cfg that lets users decide if they want to enable this feature or not. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
