Separate-mode tenant hooks never register under CAP Operator

[xyunxylona]

lib/mtx/server.js#L484 registers the per-tenant Object Store subscribe and unsubscribe handlers inside cds.on("listening", ...).

CAP Operator runs tenant operations via the cds-mtx CLI from @sap/cds-mtxs. That CLI calls cds.serve(...) and emits 'served' only (from bin/cds-mtx.js in @sap/cds-mtxs@3.9.0):

const { 'cds.xt.DeploymentService':ds, 'cds.xt.SaasProvisioningService':sps } = await cds.serve (services)
await cds.plugins
await _local_server_js()
await cds.emit('served', cds.services)

It never starts an HTTP listener, so 'listening' never fires, and the handlers are never attached. Subscribe completes successfully, zero Object Store instances are provisioned, no error, no log line. The "shared" branch's unsubscribe cleanup handler has the same problem.

Fix

Use 'served' instead. It's emitted by both cds.serve() (CLI) and cds-serve (long-running sidecar):

-cds.on("listening", async () => {
+cds.on("served", async () => {

Environment

@cap-js/attachments 3.12.1, @sap/cds 9.9.1, @sap/cds-mtxs 3.9.0, CAP Operator on Gardener with a TenantOperation workload.

[github-actions]

👋 Hello @xyunxylona, thank you for submitting this issue. Our team is reviewing your report and will follow up with you as soon as possible.

[Pavan-SAP]

Hi colleagues,
In addition, please also get rid of the profile "mtx-sidecar" and consider using multitenancy checks to ensure this is generic enough for all consumers (even though the requestor might not be using it).
The other issue: #218 was closed without an explanation.

[eric-pSAP]

Hi @xyunxylona @Pavan-SAP,

Apologies for the delayed response. Thank you for reaching out and this is something we will have a look at. Currently we are experience high capacity so there may be some delay in finding a solution, I hope that is acceptable.

@Pavan-SAP issue #218 was closed as the user who opened it no longer needed it. However, this is still an improvement we plan to add at some point soon.