If I do a tenanted deployment, that means that the whole project will be deployed multiple times - once for each tenant correct? I have one step that I need to deploy to 5 different targets with a small change in the config file for each. So as we previously talked about, I was thinking I could use tenanted deployments. But wouldn’t that execute the rest of the steps the exact same and essentially deploy to the other targets listed in the “Process” multiple times? Essentially doing redundant work?
I was thinking one could create 5 steps one after another in the process. Then could use variable replacement and transform files each step to make sure that same service has the config files changed for the new Target.
I was also thinking that one could assign all of the Targets in the process to ONE tenant and have the other 4 tenants assigned to their respective Targets for the service they are running. That way when deploying the first tenant would deploy the other services to their respective targets and the duplicated service to theirs without deploying the other services multiple times to the same target.
We have several services being deployed that all work together in our process as a flow, each service a prerequisite to the others, in an order. All of those services but 2 need to be deployed to one machine. Those other 2 services need deployed to multiple machines, each machine is a dedicated machine for a customer for that service in the flow so that we don’t have all customers on one machine and overloading it. Otherwise, all of the customers use the same machine for the rest of the steps.
Hopefully that is helpful enough to understand what I’m trying to do!
Thanks again, you’ve been great help!