Files
mesh-catalog/modules/redis/provisioner/index.ts
T
jschoubben 7b06a7a408 Event names are local now, in the manifests and in the code
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 `#`.
2026-09-27 14:42:28 +02:00

54 lines
2.3 KiB
TypeScript

// redis's provisioner — the adapter that makes redis a provider of the mesh `redis-cache`
// 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 redis creates and removes a
// per-consumer cache (novox/hq ADR 0039/0040/0048).
//
// The `redis-cache` interface: a consumer connects as `as` with the password the mesh minted, and
// stores its keys under `<as>:*`, isolated from every other consumer by an ACL user scoped to
// exactly that prefix.
//
// **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.
// redis creates exactly that login 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 { RedisClient } from "../client.js";
const redis = RedisClient.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:redis-cache] emit ${type} failed: ${err}`);
}
}
runProvisioner("redis-cache", {
async create(p: Provision): Promise<void> {
// The keyspace is scoped to the consumer's own login, so one cannot read another's keys.
const keyspacePrefix = p.as;
await redis.createAclUser(p.as, p.password, keyspacePrefix);
await announce("cache.provisioned", {
consumer: p.consumer ?? "",
username: p.as,
keyspacePrefix,
});
},
async remove(p: { as: string }): Promise<void> {
await redis.deleteAclUser(p.as);
await announce("cache.deprovisioned", { username: p.as });
},
// This server keeps its ACL users in memory only, so a restart of it forgets every consumer while
// this provisioner keeps running. Asked every minute, so a forgotten user is made again instead
// of every consumer failing to authenticate in silence (novox/hq issue 120).
async holds(p: Provision): Promise<boolean> {
return redis.holdsAclUser(p.as, p.password);
},
});