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 `#`.
52 lines
2.3 KiB
TypeScript
52 lines
2.3 KiB
TypeScript
// mosquitto's provisioner — the adapter that makes mosquitto a provider of the mesh `mqtt-topic`
|
|
// interface. The reconcile loop, the contributions file, and reading the mesh's minted password are
|
|
// the sdk harness's; this writes only the per-service half: how mosquitto creates and removes a
|
|
// per-consumer MQTT client (novox/hq ADR 0039/0040/0048).
|
|
//
|
|
// The `mqtt-topic` interface: a consumer connects as `as` with the password the mesh minted, and
|
|
// publishes and subscribes under `<as>/#`, isolated from every other consumer by a Dynamic Security
|
|
// role scoped to exactly that subtree.
|
|
//
|
|
// **The login and password are the mesh's, not the provisioner's (ADR 0048).** The mesh derives the
|
|
// login and hands it to both ends so they agree, and mints the password and delivers a copy to each.
|
|
// mosquitto creates exactly that client with exactly that password — a name or password the
|
|
// provisioner invented is one the consumer could never present.
|
|
|
|
import { runProvisioner, type Provision } from "@novox/mesh-sdk/provisioner";
|
|
import { emit } from "@novox/mesh-sdk/events";
|
|
import { MosquittoClient } from "../client.js";
|
|
|
|
const mosquitto = MosquittoClient.fromEnv();
|
|
|
|
/** Emit a lifecycle event without letting a broker hiccup fail the provisioning itself. */
|
|
async function announce(type: string, body: Record<string, string>): Promise<void> {
|
|
try {
|
|
await emit(type, body);
|
|
} catch (err) {
|
|
console.error(`[provisioner:mqtt-topic] emit ${type} failed: ${err}`);
|
|
}
|
|
}
|
|
|
|
runProvisioner("mqtt-topic", {
|
|
async create(p: Provision): Promise<void> {
|
|
// The topic subtree is scoped to the consumer's own login, so one cannot read another's topics.
|
|
const topicPrefix = p.as;
|
|
await mosquitto.createScopedClient(p.as, p.password, topicPrefix);
|
|
await announce("topic.provisioned", {
|
|
consumer: p.consumer ?? "",
|
|
username: p.as,
|
|
topicPrefix,
|
|
});
|
|
},
|
|
|
|
async remove(p: { as: string }): Promise<void> {
|
|
await mosquitto.deleteScopedClient(p.as);
|
|
await announce("topic.deprovisioned", { username: p.as });
|
|
},
|
|
// Asked every minute by the harness: whether the backend still holds this consumer exactly as
|
|
// the mesh gave it, so a login lost behind the provisioner's back is made again (novox/hq issue 120).
|
|
async holds(p: Provision): Promise<boolean> {
|
|
return mosquitto.holdsClient(p.as, p.password);
|
|
},
|
|
});
|