how do usually manage staging and production versi...
# ask-community
j
how do usually manage staging and production versions of a flow? i.e. for a single flow, deploy the latest version to staging, run it on staging, if it looks good, then push that version to production is there anything better than just copypasta the flow definition code, just with a different flow name, like a
data-ingestion-flow-staging
and
data-ingestion-flow-production
?
r
k
You can use environment variables with script based storage. This thread may help you. You can also use parameters and attach default ones to different schedules.
Michael’s suggestion here may also help you (probably read this one first before the previous link)
j
thanks so much for the tips, we ended up creating separate projects for staging and prod that worked out great, just added another
prefect register --project
line to our CI, and set up labels to separate staging and prod
🎉 2
k
Thanks for telling me @Jonathan Chu. Will include this in the list of things I tell people.