jschoubben
c82b3ff706
Mirrors the proven catalog patterns field-for-field: - lidarr -> the Servarr twin of radarr/sonarr (API v1, artist content); no provisioner (it is a consumer app). - mongodb -> postgres shape: mongodb-database provider, provisioner mints a per-consumer db+user (ADR 0053), client shells to mongosh (no npm driver, the psql convention). - mssql -> postgres shape: mssql-database provider, sqlcmd client. - mosquitto -> redis shape: mqtt-topic provider via the Dynamic Security plugin, deliberately avoiding hal's password_file (that file is nox issue 011 exactly); provisioner mints a per-consumer MQTT client+role. All four typecheck (strict, NodeNext) against the built @novox/mesh-sdk, and their service images are digest-pinned to resolved registry digests. The mesh-runtime-<mod> images keep the all-zeros placeholder the pipeline pins, as postgres/redis do, and must bundle each module's CLI (mongosh/sqlcmd/ mosquitto_ctrl) as mesh-runtime-postgres bundles psql. Not yet lab-verified: each module lists in-code what an integration test must prove (auth model, provisioner reconcile, mosquitto dynsec bootstrap ordering). Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF
47 lines
2.1 KiB
TypeScript
47 lines
2.1 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 0044/0045/0053).
|
|
//
|
|
// 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 0053).** 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("module.mosquitto.topic.provisioned", {
|
|
consumer: p.consumer ?? "",
|
|
username: p.as,
|
|
topicPrefix,
|
|
});
|
|
},
|
|
|
|
async remove(p: { as: string }): Promise<void> {
|
|
await mosquitto.deleteScopedClient(p.as);
|
|
await announce("module.mosquitto.topic.deprovisioned", { username: p.as });
|
|
},
|
|
});
|