ferruzzi commented on PR #63498: URL: https://github.com/apache/airflow/pull/63498#issuecomment-4070384379
Edge is more or less your baby, so I'm going to defer to whatever you think here. > An callback also is belonging to a Dag, Task, correct? So these details still could be used to populate details? As of right now, all deadline callbacks are tied to a dagrun. They are created and cleaned up as part of the dagrun lifecycle, so that means they obviously also have access to dag, dagbundle, serialized_dag, etc but not to Task. That may (and likely will?) change in the future, but that's what's active right now. One thing to note is that there is a lot of work going on to unify TaskInstance and ExedcutorCallback into a shared interface we're calling Workload. So pretty much anywhere that had TaskInstanceKey or something like that would ideally be migrated to use `workload.key`, for example. You can see (and review ;) ) what I think may be the last batch of those changes in https://github.com/apache/airflow/pull/63491 and an example of one of the other executors getting this treatment over in https://github.com/apache/airflow/pull/62984/ if that helps you think through what @wjddn279 is in store for. -- 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]
