Re: [I] Add ability to disable a running DAG only after after it's in a finished state [airflow]

["seub (via GitHub)" <gi...@apache.org>]

seub commented on issue #22006:
URL: https://github.com/apache/airflow/issues/22006#issuecomment-2494978052

   Just adding a comment to say that we also find that this a natural feature to request and would be very useful to deploy DAGs automatically in CI/CD.
   
   When we update a DAG in CI/CD, we'd like to be careful to avoid race conditions, therefore:
   1. Before updating the DAG, pause it and wait for any running instances to finish
   2. Update the DAG
   3. Unpause it
   
   The problem is that with the current interface and REST API offered by Airflow, it's virtually impossible to do 1. If I pause the DAG, only the current TASK instances will finish. (And if instead I wait for all the current running instances of the DAG to finish before pausing, I might wait forever as new instances can get triggered at any point)


-- 
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: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org