From 5e22e6bc49bf37099fbfc310fdf37ff0b2b7f7e9 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 1 Sep 2026 23:09:49 +0200 Subject: [PATCH] The resolve-together test carries the whole catalogue MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Eleven modules planned as one set on one machine, which is what a real node looks like. Two are left out by name rather than silently: the mesh under test already runs a module called registry and an adopted workload called umami, and adding the catalogue's manifests would replace the records of things that are live and assigned — the adopted umami would suddenly require a database it never asked for. --- test/integration/mesh.test.ts | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/test/integration/mesh.test.ts b/test/integration/mesh.test.ts index bb44396..b755f80 100644 --- a/test/integration/mesh.test.ts +++ b/test/integration/mesh.test.ts @@ -1796,7 +1796,12 @@ test("a third-party workload is adopted, with the credential it already had", { test("the real modules resolve together, and compose a declaration a host accepts", { skip, timeout: 300_000, }, async (t) => { - const modules = ["postgres", "keycloak", "gitea", "minio", "mailu"]; + // Everything the catalogue holds, except two whose names this mesh is already running under: + // `registry` is the artifact store the suite stood up, and `umami` is the adopted workload — + // adding the catalogue's manifests would replace the records of modules that are live and + // assigned, and the adopted umami would suddenly require a database it never asked for. + const modules = ["postgres", "keycloak", "gitea", "minio", "mailu", + "redis", "grafana", "nextcloud", "searxng", "influxdb", "verdaccio"]; const planned: string[] = []; for (const name of modules) { const raw = readFileSync(