Targets created with Cloud Target Discovery allow untenanted deployments when resource is tagged with a tenant

[KennethBates]

Severity

One report with a workaround

Version

2025.1.5569

Latest Version

None

What happened?

When a resource is tagged with octopus-tenant and the Cloud Target Discovery feature creates an associated target in Octopus, the target is still allowed to be deployed to without a tenant via Include in both tenanted and untenanted deployments option on the target.

When specifying the tenant on the cloud resource's tag, it is expected that the created target should be only be allowed to be deployed to when targeting the tenant.

Reproduction

Create a cloud resource tagged with octopus-tenant
Deploy a project in Octopus with Cloud Target Discovery enabled to the same tenant
See the target created

The tenant is associated with the created target, but the target is still allowed to be included in untenanted deployments

Error and Stacktrace

More Information

Report (private): https://octopus.zendesk.com/agent/tickets/220460

Workaround

Manually alter the Tenanted Deployments restriction on the target after it is created.

[Octobob]

🎉 The fix for this issue has been released in:

Release stream	Release
2025.1	2025.1.8631