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/genesis.ts
+3 -1
View File
@@ -91,7 +91,9 @@ export function stepIn(said: string): string {
export async function genesis(o: GenesisOptions): Promise<GenesisResult> {
const node = o.node;
const registry = o.registry ?? "127.0.0.1:5000";
const modules = o.catalogueModules ?? ["distribution", "mesh-controller", "builder"];
// The registry's and the builder's. Not the control plane's: its manifest lives in its own
// repository and genesis takes it from the build it runs (novox/hq ADR 0069, 04-ISSUES/072).
const modules = o.catalogueModules ?? ["distribution", "builder"];
const catalogueOnMachine = o.catalogueOnMachine ?? "/opt/mesh-catalog";
const log = o.log ?? (() => {});