novox/mesh-lab
3
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Genesis reads the registry's and the builder's manifests from the catalogue, not the control plane's

Browse Source 
The control plane's manifest comes out of the build the installer runs (novox/hq ADR
0069, 04-ISSUES/072); the catalogue no longer holds a copy, and a bed that demanded
one would stop a genesis that is about to succeed.
This commit is contained in:
jschoubben
2026-09-21 19:23:44 +02:00
parent c8c3028f38
commit 6083b9310a
3 changed files with 11 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/integration/whole-mesh-full.test.ts
+5 -3
View File
@@ -114,10 +114,12 @@ const CATALOGUE_ON_MACHINE = "/opt/mesh-catalog";
*
* Named here rather than pushing the whole repository because the whole repository is a hundred
* megabytes of `node_modules` and the installer opens exactly two files: mesh-host's
* `internal/bootstrap` RegistryModule and ControlPlaneModule. If it ever opens a third, this list
* is where the bed finds out, by the installer saying which manifest it could not read.
* `internal/bootstrap` RegistryModule and BuilderModule. (Not the control plane's: that manifest
* comes out of the build the installer runs — novox/hq ADR 0069, 04-ISSUES/072.) If it ever opens
* a third, this list is where the bed finds out, by the installer saying which manifest it could
* not read.
*/
const CATALOGUE_MODULES = ["distribution", "mesh-controller", "builder"];
const CATALOGUE_MODULES = ["distribution", "builder"];
/**
* Where this mesh keeps its own images, as the anchor reaches it.