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

The resolve-together test carries the whole catalogue

Browse Source 
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.
This commit is contained in:
jschoubben
2026-09-01 23:09:49 +02:00
parent 384e0f4e7e
commit 5e22e6bc49
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
test/integration/mesh.test.ts
+6 -1
View File
@@ -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", { test("the real modules resolve together, and compose a declaration a host accepts", {
skip, timeout: 300_000, skip, timeout: 300_000,
}, async (t) => { }, 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[] = []; const planned: string[] = [];
for (const name of modules) { for (const name of modules) {
const raw = readFileSync( const raw = readFileSync(