Uh oh!
There was an error while loading. Please reload this page.
Allowing task_group Sensor in ExternalTaskSensor - #24902
Conversation
cases
|
1425c95 to
eb29793CompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
pateash
commented
Jul 23, 2022
Hi @eladkal, could you please take a look into this PR. |
uranusjr
commented
Jul 27, 2022
Since we are already allowing multiple task IDs, I wonder if we should just go directly with |
pateash
commented
Jul 28, 2022
@uranusjr, we already allow multiple taskIds which I personally don't think a good idea, because it is not very transparent. Although For TaskGroup, I think if someone want to depend on multiple of them, they must create different task sensors. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.

closes: #14563
related: #14640
Add meaningful description above
Hi All,
This PR proposes to allow users to provide external_task_group_id in ExternalTaskSensor to make tasks on a DAG wait for another task_group on a different DAG for a specific execution_date.
we can also provide options to set if the Task on a remote DAG succeeded or failed via allowed_states and failed_states parameters.