Hi,
We’re migrating to using the Tenants feature introduced in 3.4 (currently on 3.3).
When we do our deployments we typically deploy to perhaps 1/3rd of all our Tenants in one go - and the plan is to filter to those Tenants using a tag.
However, there are times when we’ll want to exclude one or two Tenants from being deployed to (e.g. if they had a special temporary hotfix build deployed previously just for them).
Is there a way we can do that in the Tenant filter UI in the ‘Deploy To’ page?
Additionally - as a safety check, on the ‘Deploy To’ page, once we’ve chosen the Tenants to deploy to, it doesn’t show the current version that they’re on (for the current environment/project). In 3.3, when using Environments as tenants, it would show the currently deployed version for each Environment that was selected. This was very useful as a double-check to avoid accidental deployments.
Is there any way to get that feature back?
Thanks for getting in touch! We don’t have the ability to exclude some tenants when creating deployments, though I think this would be a natural fit in some situations. I’ve created this GitHub issue to track adding this enhancement: https://github.com/OctopusDeploy/Issues/issues/3336
Hi Mike,
Thanks for creating those issues, I’ll keep an eye on them.
To throw my 2cents into how this works in our usage scenario - If we were deploying to… say 40 tenants, they would be almost always chosen by filtering with just one tag. We might then want to exclude perhaps 2 or 3 of those. Excluding is certainly the exception. If we found we were excluding large amounts, and doing it often, then we would want to re-address how we’ve tagged the tenants in the first place.
So for our needs, a selection box where we can exclude multiple tenants by name would be best. Excluding based on tags etc is definitely overkill for our scenario.
I imagine there are plenty of different use-cases for Tenants, so I bet it’s tough to keep everyone happy