jschoubben
7b06a7a408
Every module named its events the way the old bus spelled a routing key — `module.<module>.<verb>`. Design 29 says a module names an event locally and the mesh works out where it lands, so all 37 were stale against a rule already decided. On the new bus that derives into a namespace belonging to a module called "module", so no cross-module subscription in the mesh matched anything: nothing failed, nothing reacted (novox/hq 04-ISSUES/127). 36 manifests converted, and 43 files of module code with them. The code mattered as much as the manifests: the runtime builds the subject from what `emit()` is handed, so a converted manifest with unconverted code would have had the permission and the subject disagree. Three things the new check found on the way: - `photos` emitted an event its manifest never declared, which the new bus refuses outright. Declared. - `showcase` waited for an event nothing emits, so its demo could never be triggered — only `showcase` may publish under its own name. It emits both halves now. - `distribution` declared an event named after a different module. It emits `image.pushed` under its own name. An event about a *role* belongs on the seat, where the name outlives whoever holds it, but the sdk has no way to publish on a seat yet, so that stays recorded rather than declared. The audit logger's "everything" pattern is `**` rather than the old bus's `#`.
26 lines
1.1 KiB
TypeScript
26 lines
1.1 KiB
TypeScript
// mssql's events entrypoint, loaded by the per-node tool host (the provisioner container runs
|
|
// ./provisioner separately). The database lifecycle events are EMITTED from the provisioner, where
|
|
// the lifecycle actually happens (novox/hq ADR 0041/0042):
|
|
// module.mssql.database.provisioned — a consumer's database + login/user was created
|
|
// module.mssql.database.deprovisioned — that database was removed
|
|
// Here in the tool host we react to them, keeping a lightweight audit trail of who was granted a
|
|
// database and who lost one — observability the provider itself is best placed to log.
|
|
|
|
import { on } from "@novox/mesh-sdk/events";
|
|
|
|
interface DatabaseEvent {
|
|
consumer: string;
|
|
database: string;
|
|
user?: string;
|
|
}
|
|
|
|
await on<DatabaseEvent>("database.provisioned", async (e) => {
|
|
console.log(`[mssql] database provisioned for ${e.body.consumer} (db ${e.body.database})`);
|
|
});
|
|
|
|
await on<DatabaseEvent>("database.deprovisioned", async (e) => {
|
|
console.log(`[mssql] database deprovisioned for ${e.body.consumer} (db ${e.body.database})`);
|
|
});
|
|
|
|
console.log("[mssql] auditing database lifecycle events");
|