The nats module, and every manifest's event names made local #115

Merged
jschoubben merged 8 commits from feat/nats-genesis into main 2026-09-27 17:31:04 +00:00
3 changed files with 3 additions and 6 deletions
Showing only changes of commit b58a3b487d - Show all commits
-3
View File
@@ -20,9 +20,6 @@
"secrets": {
"npm-package-registry": "/var/lib/mesh/builder/package-registry.secret"
},
"emits": [
"built"
],
"own-secrets": {
"broker": "/var/lib/mesh/builder/broker"
},
+2 -2
View File
@@ -1,6 +1,6 @@
// mesh-catalog's entrypoint — the module graph's consumer (novox/hq ADR 0070, ADR 0072).
//
// The builder announces what it built; this places it in the graph and announces what that means.
// The build-machine role announces what it built; this places it in the graph and announces what that means.
// The control plane hooks the *meaning* — a module was upgraded — rather than the build output, so
// it never has to interpret an artifact or ask this module anything.
//
@@ -47,7 +47,7 @@ interface Built {
replay?: boolean;
}
await on("builder.built", async (event) => {
await on("mesh-build-machine.built", async (event) => {
const body = event.body as Built;
if (!body.module || !body.commit) {
// Said rather than dropped: a build that announced itself without saying what it built is a
+1 -1
View File
@@ -29,7 +29,7 @@
"broker": "/var/lib/mesh/mesh-catalog/broker"
},
"consumes": [
"builder.built"
"mesh-build-machine.built"
],
"emits": [
"registered",