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
49 lines
2.1 KiB
TypeScript
49 lines
2.1 KiB
TypeScript
// mongodb's provisioner — the adapter that makes mongodb a provider of the mesh `mongodb-database`
|
|
// 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 mongodb creates and removes a
|
|
// consumer's database + owning user (novox/hq ADR 0044/0045/0053).
|
|
//
|
|
// The `mongodb-database` interface: a consumer connects to a database it alone owns, as `as` with the
|
|
// password the mesh minted, authenticating against that same database.
|
|
//
|
|
// **The user name and password are the mesh's, not the provisioner's (ADR 0053).** The mesh derives
|
|
// the login and hands it to both ends, and mints the password. mongodb creates a user and a
|
|
// same-named database under exactly that login — a name the consumer cannot learn is a database it
|
|
// cannot reach.
|
|
//
|
|
// The commands run through MongoClient.evalJs(), which is the module's one execution boundary (see
|
|
// client.ts).
|
|
|
|
import { runProvisioner, type Provision } from "@novox/mesh-sdk/provisioner";
|
|
import { emit } from "@novox/mesh-sdk/events";
|
|
import { MongoClient } from "../client.js";
|
|
|
|
const mongo = MongoClient.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:mongodb-database] emit ${type} failed: ${err}`);
|
|
}
|
|
}
|
|
|
|
runProvisioner("mongodb-database", {
|
|
async create(p: Provision): Promise<void> {
|
|
// Database and owning user share the consumer's login, so the consumer owns exactly its own.
|
|
const database = p.as;
|
|
await mongo.createDatabaseAndUser(database, p.as, p.password);
|
|
await announce("module.mongodb.database.provisioned", {
|
|
consumer: p.consumer ?? "",
|
|
database,
|
|
user: p.as,
|
|
});
|
|
},
|
|
|
|
async remove(p: { as: string }): Promise<void> {
|
|
await mongo.dropDatabaseAndUser(p.as, p.as);
|
|
await announce("module.mongodb.database.deprovisioned", { database: p.as });
|
|
},
|
|
});
|