we just started designing our deployment process in Octopus and so far everything works flawless.
So, we have a white-label software that we deploy to 5 different customer systems, each with a testing/prod environment. We created 5 tenants for our customers and have a deployment process running for that. Let’s name them “customer1… to customer5”.
Each of our customers is again serving 2-15 customers with our software. We created tenants for each customer’s customer and have a second project that deploys stuff specfic for that “subcustomer”. That works fine so far. Let’s name them “customer1:subcostumerA…to customer1:subCustomerZ, customer2:subCostumerA…to customer2:subCostumerF and so on”
Now, we have a third party software (a windows service) that needs to be deployed 1-5 times per subCustomer.
I found something like this here. The advice there is to add additional tenants for each service.
I’m tempted to do this and add a multitude of tenants, using tags to group them. We’ll end up with > 100 tenants for this specific service then. My questions are:
- Is that a valid solution?
- Or is there something like “tenants-in-tenants” I’m missing?
- Is it ok to use multi-tenancy for different purposes ("customers as tenants and “multiple 3rd-party-services as tenants”)?
- If we go the way described above: Is there a limit of tenants or something else like that?
Thx a lot!