Pad71 commented on issue #53402: URL: https://github.com/apache/airflow/issues/53402#issuecomment-3078172621
> I think Elad is right, and the closest we had in AF2 was `recursive` option in clear. I also agree that this shouldn't be controlled by the operator but by the UI. > > Recursive controlled `include_subdags` and `include_parentdag`. (is_subdag, parent_dag, etc.) All that was removed with airflow 3 removal of subdags. > > Also I don't think this would handle 'external triggers', only subdags (here i'm not sure), so this request might be slightly different and still make sense for AF3. (we want to clear external dependencies basically) hello @pierrejeambrun Again, if it is done by UI, it's ok. Problem is, that we can't do it now and it is realy painful for operations team (in our company we have lot's of dags triggered by triggerdagrunoperator tasks). Recursive option does not work for that use case. -- 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]
