alex-astronomer commented on issue #18410: URL: https://github.com/apache/airflow/issues/18410#issuecomment-933594206
@eladkal Great point. I still do believe that the DAGs should be paused and unable to run in this situation. Here's my reason for that. If suddenly there is an AirflowClusterPolicy that is implemented that would disable 50 DAGs shouldn't that be done, just because if the policy is violated then we don't want to be able to run the DAGs anyway? I understand what you're saying is that it would be hard to know what DAGs were paused and it would be hard to revert. I think that a way that we could get around this shortcoming is audit logging for the DAGs that were paused and putting some logs saying what happened in the Logs section of Airlfow. What do you think about that? -- 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]
