Wojciech Kieliszek
11/28/2022, 2:59 PMserialized_hash()
value as an idempotency_key
and as a docker storage tag. That way we don’t bump the versions when there is no change in a flow “schema”. But this mechanism allows us also to redeploy a docker image for the same flow version (no change in idempotency_key
) to change logic of particular tasks when there is no change of the “contract”. So for long running flows runs we can change their behaviours to some extent during their execution or resume them after a failure with new bug-free logic. We are now in transition to Prefect v2. Is there any kind of similar mechanism available in Prefect v2?Mason Menges
11/28/2022, 8:54 PM