Jacob Blanco05/25/2022, 2:29 AM
Samuel Hinton05/25/2022, 2:54 AM
- if so, using CLI prefect register instead can help here as it automatically detects flow changes and you can use it to register only directories relevant for your team - say, if data scientists have their own folder in your shared repo, their CI/CD workflow might include the command:
prefect register --project xxx -p data_science_flows/
Jacob Blanco05/26/2022, 1:27 AM
and we don’t calculate our own and instead use the git diff between the latest staging/production tag and the latest production tag (which is an imperfect solution of course). We are indeed using
so your point still stands.
Jacob Blanco05/31/2022, 2:35 AM
Jacob Blanco06/08/2022, 2:11 PM
before we dive deeper here and before you start any process optimizations - what’s your upgrade plan to Prefect 2.0? not sure whether optimizing the process for 1.0 makes sense now - it depends on when/how do you plan to migrateWe are still waiting on confirmation of when Prefect 2.0 will be released so that we can start working backwards towards an upgrade plan. We are in the midst of renewing our contract are moving to 2.0 as a result. I’ve not had a deep look at 2.0 and how that impacts deployment yet, but I think philosophically speaking separating the dependency from the flow definition makes sense regardless. I’ll take a look more deeply at 2.0 and see what our to-be deployment pipeline should look like, and maybe come back with more specific questions. Thanks.
separating the dependency from the flow definition makes sense regardlessCouldn't agree more! 💯 That makes sense. Keep us posted!