Jeff Brainerd
12/29/2020, 9:11 PMversion_group_id
when we register flows to differentiate the environment (i.e. prod, staging, etc). Not only do they run in separate environments, those flows all have separate version history as well. I see in the docs that version_group_id
is deprecated. So what’s the best practice for differentiating flow groups for separate environments? Should we use the env as part of the flow name, e.g. my_flow_prod
? And if that’s the case, does Project + Name uniquely identify the flow? Thanks!Jim Crist-Harif
12/29/2020, 9:37 PMversion_group_id
in favor of a similar mechanism, but that deprecation hasn't completed yet. See https://prefect-community.slack.com/archives/CL09KU1K7/p1608758775445500?thread_ts=1608756725.445100&cid=CL09KU1K7 for more info.Local
storage you'll need to explicitly specify a path (since the default path doesn't take the project into a ccount), but other than that things will work fine.Amanda Wee
12/29/2020, 9:42 PMLocal
storage, and don't specify the path, they will use the same path and hence the flow registered later will "override" the flow registered earlier?Jim Crist-Harif
12/29/2020, 9:44 PMAmanda Wee
12/29/2020, 9:45 PMJim Crist-Harif
12/29/2020, 9:46 PMAmanda Wee
12/29/2020, 10:10 PMJeff Brainerd
12/29/2020, 10:48 PM