LMnet opened a new issue, #37730: URL: https://github.com/apache/airflow/issues/37730
### Description I found that for tasks within setup/teardown block, you can use only `ALL_SUCCESS` trigger rule. It feels very limiting. For example, I have a use case when I submit a bunch of jobs to an AWS EMR cluster. Jobs are independent, but I want to submit them one by one to not overflow the cluster. So currently I can't implement this kind of logic together with setup/teardown. ### Use case/motivation _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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-unsubscr...@airflow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
