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 `#`.
45 lines
2.3 KiB
TypeScript
45 lines
2.3 KiB
TypeScript
// keycloak's events. Keycloak's worth to the mesh is in what it changes — an identity created, a
|
|
// client registered, a password reset — so its events are emitted from the admin actions themselves
|
|
// (novox/hq ADR 0041/0042), not scraped back by polling. This module is the single vocabulary for
|
|
// them: every keycloak event goes through one of the helpers here, and the tools call them at the
|
|
// point the change succeeds.
|
|
//
|
|
// Emits:
|
|
// module.keycloak.user.created / .deleted — an identity appeared or was removed
|
|
// module.keycloak.password.reset — a user's credential was reset (no secret in the body)
|
|
// module.keycloak.client.created — an OIDC client was registered
|
|
// module.keycloak.group.created — a group was created
|
|
// module.keycloak.role.created — a realm role was created
|
|
// Consumes:
|
|
// nothing — Keycloak is upstream of the things that authenticate against it; it reacts to none of
|
|
// their events. There is no honest `on(...)` to write, so there is none.
|
|
|
|
import { emit } from "@novox/mesh-sdk/events";
|
|
|
|
// A completed admin action must not be undone by a flaky broker: the change already happened in
|
|
// Keycloak, so a failed emit is logged and swallowed rather than thrown back through the tool.
|
|
async function announce(type: string, body: Record<string, unknown>): Promise<void> {
|
|
try {
|
|
await emit(type, body);
|
|
} catch (err) {
|
|
console.error(`[keycloak] emit ${type} failed: ${err}`);
|
|
}
|
|
}
|
|
|
|
export const events = {
|
|
userCreated: (realm: string, username: string, email?: string) =>
|
|
announce("user.created", { realm, username, ...(email ? { email } : {}) }),
|
|
userDeleted: (realm: string, userId: string) =>
|
|
announce("user.deleted", { realm, userId }),
|
|
passwordReset: (realm: string, userId: string) =>
|
|
announce("password.reset", { realm, userId }),
|
|
clientCreated: (realm: string, clientId: string, name?: string) =>
|
|
announce("client.created", { realm, clientId, ...(name ? { name } : {}) }),
|
|
groupCreated: (realm: string, name: string) =>
|
|
announce("group.created", { realm, name }),
|
|
roleCreated: (realm: string, name: string) =>
|
|
announce("role.created", { realm, name }),
|
|
};
|
|
|
|
console.log("[keycloak] event surface ready — identity, client, group and role changes are announced");
|