Hi all, we are about to migrate to prefect 3, is t...
# ask-community
a
Hi all, we are about to migrate to prefect 3, is there any breaking changes if we only update the server but keep the code and its
@flows
and all their attributes 🙂 ? Thanks !
b
Hi Alexis! The main thing that I can think of is that agents,
prefect deployment build
, and
Deployment.build_from_flow()
are deprecated in Prefect 3.0. There are much better alternatives available for all of these. Here are some docs that talk about these changes in more detail: • Upgrade from agents to workersUpgrade to Prefect 3
upvote 1
Check out the upgrade notes in "Upgrade to Prefect 3" for the full list.
What you're gaining from 3.0 will definitely outweigh the breaking changes. If you notice any friction points, or want to suggest documentation for something, tell us in GitHub!
a
thanks a lot @Bianca Hoch
👍 1
💯 1
c
So, Can I upgrade our self-hosted prefect server to 3, but leave the process worker as 2.20 ? and maybe alternatively set up a second worker that’s using prefect 3, then migrate deployments to the version 3 worker? ( so we can test them individually and not have to big-bang upgrade and risk downtime ).
b
Hi Corris, my recommendation would be running two servers (2.0 and 3.0), two workers (2.0 and 3.0), and then re-deploying your 2.0 flows to your 3.0 worker and server one at a time.
Running a 2.0 worker against a 3.0 server may cause some compatibility issues
so we can test them individually and not have to big-bang upgrade and risk downtime
plus1 plus1 plus1 plus1 to this, good thinking.
c
Hi @Bianca Hoch, Thanks, that’ll work. now to decide if I use prefect.domain.tld or prefect3.domain.tld …. I’m currently using prefect2.domain.tld lol. https://xkcd.com/910/
127 Views