Channels
pacc-may-31-2023
prefect-ai
pacc-clearcover-june-12-2023
marvin-in-the-wild
data-ecosystem
geo-israel
pacc-june-14-2023
geo-japan
prefect-cloud
ppcc-may-16-2023
prefect-azure
prefect-docker
prefect-recipes
gratitude
geo-nyc
geo-bay-area
geo-boston
geo-london
geo-dc
geo-chicago
geo-berlin
geo-texas
geo-seattle
geo-colorado
prefect-community
data-tricks-and-tips
prefect-aws
prefect-gcp
introductions
find-a-prefect-job
prefect-dbt
random
events
ask-marvin
show-us-what-you-got
prefect-getting-started
prefect-integrations
prefect-contributors
best-practices-coordination-plane
announcements
prefect-server
prefect-ui
prefect-kubernetes
Title
s
Stephen Lloyd
09/20/2022, 3:17 AMIs there anything comparing Prefect 1.0 vs 2.0 concepts? Are 2.0 work queues roughly equivalent to 1.0 projects?
c
Christopher Boyd
09/20/2022, 1:45 PMHI Stephen,
We have an entire slew of documentation on discourse and youtube targeting this exact question. https://discourse.prefect.io/search?q=migrate%20from%201.0
Work queues are just a way to isolate your data and runs. In that sense, they can be similar to projects,
For setting up dev, uat, prod, it depends on your infrastructure setup. One common way is to use deployments , and infrastructure blocks
An infrastructure block can be created with one set of storage, and executing infrastructure, with parameters / overrides, and another infrastructure block with another set (dev, vs prod). Then creating a flow run from one or the other would execute against that environment
s
Stephen Lloyd
09/20/2022, 1:48 PMOk, so it’s possible to have three separate environments running without 3 separate workspaces?
We’re on 1.0 and use projects to separate environments.
I’d like to move to 2.0 without complete upheaval. Looking for the most graceful way without having 3 separate workspaces.
c
Christopher Boyd
09/20/2022, 1:51 PMFrom the data / execution side, absolutely.