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
1.9 KiB
TypeScript
52 lines
1.9 KiB
TypeScript
// registry's events. The tool runtime imports this once the broker is bound.
|
|
//
|
|
// Emits (novox/hq ADR 0041/0042):
|
|
// module.registry.image.pushed — a new image (repo:tag) was published to the registry
|
|
//
|
|
// This is a genuinely useful signal: a build finished and its image is now pullable, so anything
|
|
// on the mesh that redeploys, mirrors or announces releases can react without polling the registry
|
|
// itself. It is discovered by diffing the catalog and each repo's tags — the registry has no push
|
|
// webhook of its own, so the module watches for it.
|
|
//
|
|
// The polling is deliberately unhurried: a new image a minute late is still the event, whereas
|
|
// hammering the registry's catalog for immediacy nobody asked for is not.
|
|
|
|
import { emit } from "@novox/mesh-sdk/events";
|
|
import { RegistryClient } from "./client.js";
|
|
|
|
const registry = RegistryClient.fromEnv();
|
|
|
|
// Every repo:tag we have already accounted for. Primed silently on the first look so a registry
|
|
// that was already full when this started does not announce its whole history as freshly pushed.
|
|
const seen = new Set<string>();
|
|
let primed = false;
|
|
|
|
async function pollCatalog(): Promise<void> {
|
|
const repos = await registry.listRepositories();
|
|
for (const repo of repos) {
|
|
let tags: string[];
|
|
try {
|
|
tags = await registry.listTags(repo);
|
|
} catch {
|
|
continue; // a repo can vanish between catalog and tag read — skip it, catch it next tick
|
|
}
|
|
for (const tag of tags) {
|
|
const id = `${repo}:${tag}`;
|
|
if (!seen.has(id)) {
|
|
if (primed) await emit("image.pushed", { repo, tag });
|
|
seen.add(id);
|
|
}
|
|
}
|
|
}
|
|
primed = true;
|
|
}
|
|
|
|
const tick = (fn: () => Promise<void>, everyMs: number): void => {
|
|
const run = (): void => void fn().catch((err) => console.error(`[registry] ${err}`));
|
|
setInterval(run, everyMs);
|
|
run();
|
|
};
|
|
tick(pollCatalog, 60_000);
|
|
|
|
console.log("[registry] watching the catalog for newly pushed images");
|