Uh oh!
There was an error while loading. Please reload this page.
AIP-84 Add external dependencies to GET Structure Data Endpoint - #44701
Conversation
Uh oh!
There was an error while loading. Please reload this page.
46ee957 to
64f3cc9Compared76d6b1 to
8789aaaCompareUh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
5ea5c6f to
87b5121Compare
bbovenzi
left a comment
There was a problem hiding this comment.
Testing locally, I noticed two issues:
example_external_task_marker_parent: did not have any downstream deps
example_trigger_controller_dag`: the dependency comes back as upstream when it should be downstream
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Indeed. That's a limitation we have at the moment in the backend in I will open a dedicated issue to track that because its not straight forward. edit: Dedicated issue here #44879 |
pierrejeambrun
commented
Dec 12, 2024
Good catch, fixed, also added a test for that. |
…he#44701) * Working state * Add tests for external task sensor * Add test for TriggerDagRunOperator * Fix following code review * Update following code review
…he#44701) * Working state * Add tests for external task sensor * Add test for TriggerDagRunOperator * Fix following code review * Update following code review
Related to: #42367
Adds the
external_dependenciesquery parameter.Supports
trigger,sensor,asset,asset_aliases.Sensor is back because
ExternalTaskSensoris creating asensordependency type.For now all that is
externalto the dag, and not specific to thetask_level. Meaning that they are attached to the dag (first task of the dag) and not to the specific tasks. (i.e task outlets for assets for instance)