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 `#`.
49 lines
2.4 KiB
TypeScript
49 lines
2.4 KiB
TypeScript
// mesh-vault's provisioner — the adapter that makes vault a provider of the mesh `secret` interface. The
|
|
// reconcile loop, the contributions file, and reading the mesh's minted value are the sdk harness's;
|
|
// this writes only the per-service half (novox/hq ADR 0039/0040/0048) — and for a vault that half is
|
|
// taking custody, not creating anything.
|
|
//
|
|
// The `secret` interface (ADR 0085, design 24): a consumer requires a value for its own use — the
|
|
// password of a store it runs privately, an internal token — and reads it from the file the mesh
|
|
// writes on its machine. There is no server to create a login on. **The value is the pair
|
|
// credential itself**: the controller minted it, sealed it to both nodes, and delivered each its
|
|
// copy. What makes it *owned* is this: the vault records who holds it and its fingerprint, notices
|
|
// when `rotate secret` delivers a different one, and says so on the mesh. Rotation is not new
|
|
// machinery — it is the machinery that already moves a database password, pointed at a secret the
|
|
// vault provides (design 13).
|
|
|
|
import { runProvisioner, type Provision } from "@novox/mesh-sdk/provisioner";
|
|
import { emit } from "@novox/mesh-sdk/events";
|
|
import { Ledger } from "../client.js";
|
|
|
|
const ledger = Ledger.fromEnv();
|
|
|
|
/** Emit a lifecycle event without letting a broker hiccup fail the custody itself. */
|
|
async function announce(type: string, body: Record<string, string | number>): Promise<void> {
|
|
try {
|
|
await emit(type, body);
|
|
} catch (err) {
|
|
console.error(`[provisioner:secret] emit ${type} failed: ${err}`);
|
|
}
|
|
}
|
|
|
|
runProvisioner("secret", {
|
|
async create(p: Provision): Promise<void> {
|
|
const { held, outcome } = ledger.record(p.as, p.consumer ?? "", p.password);
|
|
if (outcome === "unchanged") return; // the harness re-runs create on restart; nothing happened
|
|
console.log(`[mesh-vault] ${outcome}: ${held.as} (${held.fingerprint.slice(0, 19)}…, rotations ${held.rotations})`);
|
|
await announce(`module.mesh-vault.secret.${outcome === "granted" ? "provisioned" : "rotated"}`, {
|
|
consumer: held.consumer,
|
|
as: held.as,
|
|
fingerprint: held.fingerprint,
|
|
rotations: held.rotations,
|
|
});
|
|
},
|
|
|
|
async remove(p: { as: string }): Promise<void> {
|
|
if (!ledger.withdraw(p.as)) return;
|
|
console.log(`[mesh-vault] withdrawn: ${p.as}`);
|
|
await announce("secret.deprovisioned", { as: p.as });
|
|
},
|
|
});
|