07/09/2023, 10:20 AM
Dear all, I guess there are many ways to Rome, but
how does prefect suggest to set up CICD workflows to deploy flows in dev, staging and production environments
? I set up a CICD pipeline, in which I once want to check in a staging environment whether the flows run properly on the staging infrastructure, before deploying the flows to production. Does it therefore make sense to have ā€¢ one work queue for each environment ā€¢ one deployment for each environment Currently, I create an
{environment} deployment
and a
{environment} work queue
{environment} specific infrastructure
so that I can make a full integrated test and avoid that a staging flow is run on the production infrastructure in the same
general work queue
. One could of course argue that one may differentiate between "infrastructure environment" and "runtime environment" etc. but that may make things more complicated. Maybe I am also overcomplicating things and prefect has a simple, elegant solution for this? šŸ¤”


07/09/2023, 12:05 PM
I prefer 1 workspace per environment, of course there are cost implications however I prefer everything to be isolated and no danger of crossing the streams, also reduces confusion
šŸ™Œ 1
Each workspace is then identical apart from env variables/secrets to point to databases/storage etc


07/09/2023, 12:45 PM
Oh yeah, that makes sense