jschoubben
6615b5e3b3
plex gains a broker-bound tools/events runtime container (mesh-runtime-plex) alongside its server, and a never-throwing plex_reachable health probe. redis and postgres subscribe to their own lifecycle events in index.ts but declared no consumes — so the substrate never made the queue the runtime binds and it crashed on start (404). Declare the consume, as ADR 0046 requires. Proven end-to-end in the mesh-lab: assigned-plex and assigned-redis both green. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
26 lines
1.2 KiB
TypeScript
26 lines
1.2 KiB
TypeScript
// postgres'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 0046/0047):
|
|
// module.postgres.database.provisioned — a consumer's database + owning role was created
|
|
// module.postgres.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>("module.postgres.database.provisioned", async (e) => {
|
|
console.log(`[postgres] database provisioned for ${e.body.consumer} (db ${e.body.database})`);
|
|
});
|
|
|
|
await on<DatabaseEvent>("module.postgres.database.deprovisioned", async (e) => {
|
|
console.log(`[postgres] database deprovisioned for ${e.body.consumer} (db ${e.body.database})`);
|
|
});
|
|
|
|
console.log("[postgres] auditing database lifecycle events");
|