https://prefect.io logo
Title
s

Shaoyi Zhang

07/21/2022, 10:29 PM
Prefect 1.0 - Why Prefect don’t recommend forcing version update when the flow metadata didn’t change? Having an updated timestamp on the flow helps user understand when the flow was updated without going back to git repos or CI/CD pipelines logs.
1
a

Anna Geller

07/21/2022, 10:43 PM
by default when your metadata doesn't change, your version doesn't get incremented
so it seems to work exactly as you described
s

Shaoyi Zhang

07/21/2022, 10:45 PM
yes, I understand the default behavior and we can force version bump, but just curious on why it’s the default behavior
a

Anna Geller

07/21/2022, 10:45 PM
it's explained on Discourse
👀 1
s

Shaoyi Zhang

07/21/2022, 10:54 PM
If I understand correctly, if we moved to pickled storage, the version number and the timestamp will change every time we modify and register the flow source code. The pros with pickled storage is it “froze your flow at registration time”. The cons are it’s easier to break between Prefect version upgrades. So forcing the flow registration with script based storage fits our use case. Will there be performance limitations with forcing registrations since that’ll generate a ton of versions?
a

Anna Geller

07/22/2022, 12:33 AM
no, it won't
:thank-you: 1
besides, this will not matter as much once you migrate to Prefect 2.0 as flow version changes are more lightweight
s

Shaoyi Zhang

07/22/2022, 12:34 AM
sounds great! Thank you!
🙌 1