Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update triggering asset events key type #47282

Draft
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

Lee-W
Copy link
Member

@Lee-W Lee-W commented Mar 3, 2025


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

Lee-W added 2 commits March 3, 2025 11:40
@@ -947,7 +947,7 @@ def get_prev_start_date_success() -> pendulum.DateTime | None:
def get_prev_end_date_success() -> pendulum.DateTime | None:
return timezone.coerce_datetime(_get_previous_dagrun_success().end_date)

def get_triggering_events() -> dict[str, list[AssetEvent]]:
def get_triggering_events() -> dict[Asset, list[AssetEvent]]:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we should use a custom mapping class like OutletEventAccessors so we can accept AssetRef here; it is a bit clunky for users to need to pass in the original asset object to get events.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep, sounds like a good idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants