From 833d8ec3ec727008e6157f91995892a2781d910d Mon Sep 17 00:00:00 2001 From: jochen Date: Wed, 23 Sep 2026 23:40:54 +0200 Subject: [PATCH] The artifact store's seat is one per mesh Review of the registry work found it node-scoped: a second `distribution` on another machine resolved cleanly there, and only afterwards did the mesh notice `artifact-store` offered by two nodes, with every consumer elsewhere refusing to choose. Worse, a node-scoped requirement with one candidate installs that candidate, so anything that wanted the store beside it would have raised a fresh, empty store on the wrong machine first. There is one store in a mesh, which was already the effective rule; the claim now says it where a second one is assigned, by name, instead of leaving consumers to discover it. --- modules/distribution/module.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/distribution/module.json b/modules/distribution/module.json index 029fb04..e22180b 100644 --- a/modules/distribution/module.json +++ b/modules/distribution/module.json @@ -10,7 +10,7 @@ "claims": [ { "name": "the-artifact-store", - "scope": "node" + "scope": "mesh" } ], "capabilities": [ -- 2.54.0