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.

This commit is contained in:

jschoubben

2026-09-23 23:40:54 +02:00

parent 9f2c678355

commit 833d8ec3ec

1 changed files with 1 additions and 1 deletions

									
										modules/distribution/module.json
									
		+1
		-1
	
												View File
												
				@@ -10,7 +10,7 @@

				  "claims": [

				    {

				      "name": "the-artifact-store",

				      "scope": "node"

				      "scope": "mesh"

				    }

				  ],

				  "capabilities": [