Hi all, question on deploying flows with multiple ...
# ask-community
l
Hi all, question on deploying flows with multiple agents. If I have version 1 of my flow deployed to an agent with label ‘prod’ and I want to test out a new feature on an agent with label ‘dev’. Will this new flow deployment of version 2 on agent dev have an effect on my version 1 flow already running on agent with label ‘prod’?
k
Hey @Leon Kozlowski If already running there will be no effect, but it would affect subsequent runs.
l
Even if it is deployed with only the ‘dev’ label?
The workflow I’m thinking about is something like: Once a flow is merged up to a development branch Register flow to dev agent with ‘dev’ label Once a flow is merged up to a main branch (after testing on dev agent) Register flow to prod agent with ‘prod’ label Is this possible with 1 tenant?
k
The label is attached to the Flow group so when you register with
dev
, the
prod
label is overwritten and you only have one copy of the Flow with the
dev
label. This is a lot easier on two tenants as you would switch between the tenants but on 1 tenant, you would register the flow under a
dev
project and a
prod
project, which would give you two copies of the Flow. These two copies would then have the respective labels. When you want to bring the
dev
into
prod
, it would be a
re-registration
in the prod project. It may help the workflow if you use the CLI (and maybe a Makefile) to register to the
prod
project when you want to.
l
Is it common to use projects for environments?
k
Yes it is! A lot of users have multiple environments and manage them with projects + labels as opposed to creating a new tenant
l
Ok - I will use that approach for now, appreciate it @Kevin Kho
👍 1