Skip to content
This repository has been archived by the owner on Sep 4, 2024. It is now read-only.

Launch Operator trigger_rule Option #58

Open
leungadrian opened this issue Jan 17, 2024 · 0 comments
Open

Launch Operator trigger_rule Option #58

leungadrian opened this issue Jan 17, 2024 · 0 comments

Comments

@leungadrian
Copy link

Currently the launch operator defaults to 'all_success' and it doesn't appear to have an option to pass trigger_rule's to this operator. Thus when any task upstream is skipped, the launch task skips and linked tasks fail, despite differing trigger_rule's applied to the DatabricksNotebookOperator's.

Is it possible to pass trigger_rule's to this Operator, and if not can this functionality be added?

@leungadrian leungadrian changed the title 'launch' Operator trigger_rule Option Launch Operator trigger_rule Option Jan 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant