IAdapterTenantScope

Namespace: Meshmakers.Octo.Sdk.Common.Services

The tenant the current pipeline execution is acting for (AB#4924, increment 3).

public interface IAdapterTenantScope

Remarks:

🔴 This exists because AdapterOptions.TenantId was deleted, not deprecated. A process-wide tenant value is the whole hazard of shared adapter leasing: while one exists, any service or node can read it instead of the tenant of the work item it is actually running, and the wrong answer looks entirely plausible in a log. Deleting the property turns every such read into a compile error, and this interface is what the reads become.

The value is per execution, not per process, and it is set that way TODAY — on a dedicated adapter it happens to equal the adapter's own tenant on every execution, which is why increment 3 is behaviour-preserving. Nothing about this contract changes when leasing arrives; only who supplies the value does.

Prefer IEtlContext.TenantId / INodeContext inside a node — the node layer already carries the tenant explicitly and does not need this. This interface is for the services around the node layer (HTTP routing, token acquisition, caches) that used to reach for the process-wide value.

Properties

IsPoolMember

Whether this process serves more than one tenant over its lifetime, one lease at a time.

public abstract bool IsPoolMember { get; }

Property Value

Boolean

Remarks:

Always false in increment 3 and for every dedicated adapter. It is not configurable: a process that is not built as a pool member must not be able to become one by environment variable. Increment 6 supplies the implementation that can return true.

HasTenant

Whether a tenant is currently in scope. False outside any execution, and on a pool member between leases.

public abstract bool HasTenant { get; }

Property Value

Boolean

TenantId

The tenant of the current execution.

public abstract string TenantId { get; }

Property Value

String

Exceptions

InvalidOperationException
No tenant is in scope. Deliberately an exception rather than a null or a fallback to some ambient default: a caller that reaches for the tenant outside an execution has a bug, and the one thing that must never happen is for it to receive a plausible-looking wrong answer.

Methods

BeginExecution(String)

Enters the tenant for one execution. Dispose to leave it.

IDisposable BeginExecution(string tenantId)

Parameters

tenantId String

Returns

IDisposable

Remarks:

Nested entries are permitted and restore the previous value on dispose — a node that starts a sub-pipeline runs inside the outer execution's scope.