Answering customer feedback, Octopus Deploy is adding support for deactivating tenants to its deployment team tool.
Also, they’re removing deactivated tenants from license calculations, according to Isaac Calligeros, blogging for Octopus.
Deactivated tenants prevent deployments and runbook runs but remain editable. Octopus offers deployment automation for .NET servers.
“The ability to deactivate tenants gives you greater flexibility and control over your deployments,” he explained.
Tenant deactivation rolls out to Cloud customers first and to its self-hosted customers in the 2025.1 release.
“This feature makes it simple to prevent deployments to specific tenants, manage licensing requirements, and keep your environments organised without losing access to historical configurations.”
Tenants can now be grouped by enabled or disabled status, via the tenant settings page, tenants and project tenants pages.
You can still edit, add, or remove deactivated tenants from any related entities. In these scenarios, you can identify deactivated tenants by their deactivated chip state, Calligeros noted.
Additionally, user interface (UI), command-line interface (CLI) and Terraform provider support made managing tenant states possible anywhere.
“We’re keen to hear how this feature helps you simplify your processes,” Calligeros said. “Let us know.”
Planning more deployment team tool improvements
Also, Octopus seeks comments and feedback on future improvements. Get in touch here.
.NET developers can use Octopus for software pipeline building tasks such as promoting releases between environments or limiting who can deploy to production.
It can also help ensure releases have been tested first, schedule deployments for later, or block promotion of broken releases, with a focus on continuous delivery (CD).
Octopus’ agent Tentacle supports deployment to virtual machines VMs on-prem or hosted in AWS EC2 or Azure.
