One wrinkle to the have cake and eat it too approach is deferrable
operators. It doesn't seem it would be very practical to resume back into
the operator that is nested inside a taskflow function. One solution would
be to run the trigger in process like we currently do with `dag.test()`.
That
I guess PR to propose something for that would be a good start :). I I
am fine - for now with forbidding it "as-is" and then maybe next step
once we do it is to figure out a nicer way of doing it than Hooks.
Maybe it can be done in parallel.
On Fri, Mar 1, 2024 at 9:19 PM Blain David wrote:
>
>
+1 (binding): verified reproducibility (yay - works nicely finally !),
signatures, checksums, licences. Installed Airflow 2.8.2 in kind
cluster using the "rc1" - published chart., played a bit with it - ran
a few DAGs using Breeze - using the same version as released in the
Helm Chart - all looks
