jochen
08265a70ca
Both caught a failed write and took the event, losing it silently; the SDK's rule is to throw when the work was not done. A failed write now throws so the bus offers the event again, and is spooled on disk at once; on its last delivery the spooled event is taken, and a background pass replays the spool once writing works. The runtime does not pass the delivery count, so the spool counts failed deliveries itself, across restarts. Over its bound (1000 events or 30 minutes) the last delivery is no longer taken, so the bus gives it up and the controller raises max-deliveries - the one existing condition that names a consumer which cannot keep up - while the spool still holds it. Writes are idempotent by event: the trail skips an id it already wrote; the usage upsert keeps the reading observed latest (migration 2), so a late replay never overwrites a newer one. Each module has a status tool for the spool, declared as valuable data (ADR 0233). model-usage moves to the bundle shape (ADR 0198) with its schema in a prepare step and numbered migrations; its old container shape had no image. Both on mesh-sdk 0.1.13. The log-only handlers of redis, mssql, mosquitto, mongodb, mesh-vault, showcase and the catalogue no longer throw a TypeError on an event without a body.
26 lines
1.1 KiB
TypeScript
26 lines
1.1 KiB
TypeScript
// mosquitto's events entrypoint, loaded by the per-node tool host (the provisioner container runs
|
|
// ./provisioner separately). The topic lifecycle events are EMITTED from the provisioner, where the
|
|
// lifecycle actually happens (novox/hq ADR 0041/0042):
|
|
// module.mosquitto.topic.provisioned — a consumer's client + scoped role was created
|
|
// module.mosquitto.topic.deprovisioned — that client was removed
|
|
// Here in the tool host we react to them, keeping a lightweight audit trail of who was granted a
|
|
// topic namespace and who lost one — observability the provider itself is best placed to log.
|
|
|
|
import { on } from "@novox/mesh-sdk/events";
|
|
|
|
interface TopicEvent {
|
|
consumer: string;
|
|
username: string;
|
|
topicPrefix?: string;
|
|
}
|
|
|
|
await on<TopicEvent>("topic.provisioned", async (e) => {
|
|
console.log(`[mosquitto] topic provisioned for ${e.body?.consumer} (client ${e.body?.username})`);
|
|
});
|
|
|
|
await on<TopicEvent>("topic.deprovisioned", async (e) => {
|
|
console.log(`[mosquitto] topic deprovisioned for ${e.body?.consumer} (client ${e.body?.username})`);
|
|
});
|
|
|
|
console.log("[mosquitto] auditing topic lifecycle events");
|