mesh-controller

2,522 Commits 35 Branches 1 Tag

3 Commits

Include renames

Author	SHA1	Message	Date
mesh-tools	af267cb557	Take the catalogue from mesh-sdk in internal/inventory and internal/link, and keep the tests that read this repository's own manifest, Dockerfile and Makefile in internal/ownmanifest (issue 1381, 5 of 6 import swaps) The three tests of the controller's own module.json (process, claimed seat, addresses), the Dockerfile and Makefile pin test, the build-agent registry test and the manifest-in-use seat test move with their old package, as tests of mesh-sdk's exported API; a moved test is exempt from failing first.	2026-10-20 08:27:10 +00:00
jschoubben	66dc501fc4	Split the unit level from the integration level in cmd, builder, link, catalogue, inventory; cheap fixtures for the archive-entry bound, the registry waits and the catalogue copy (issue 895)	2026-10-17 21:32:23 +02:00
jochen	c9dd07f919	Never make a credential only a person can give, and give it once per provider (hq issue 164, ADR 0337) mesh/merge-gate head c9dd07f919a2 merged into trunk 404b4409e70e — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every … Details mesh/repo-check head c9dd07f919a2 merged into trunk 404b4409e70e — pass: its merge-check.sh passed (run 2) Details mesh/delivery delivered Details A Servarr app's API key, an indexer's key and a downloader's password are values the provider's software holds; the pair path made a random value for every consumer of them, sealed it to both ends and reported success, and the provider refused it. An offer may now say `"credential": {"issued-by": "outside"}`: SecretFor never makes a value for it, the plan reads such a pair as given or not given and sends the consumer no credential file until a person gives it, without refusing its machine; remakeShared and SharedSecretFor never make a provider's own secret issued outside either. `secret accept <provider's node> <provider module> <provision>` seals one value to every consumer that binds the provision from that provider, the provider and the operator, under one generation; the per-pair form is refused for such a provision, and rotate names the accept. A consumer may wait for a provision's credential: the controller excuses the wait only when the store bears it out, and its needs-operator condition names the one accept line. Adds the replay of issue 164 (TestReplay164), written with only what the controller had before.	2026-10-13 11:37:31 +02:00

Author

SHA1

Message

Date

mesh-tools

af267cb557

Take the catalogue from mesh-sdk in internal/inventory and internal/link, and keep the tests that read this repository's own manifest, Dockerfile and Makefile in internal/ownmanifest (issue 1381, 5 of 6 import swaps)

The three tests of the controller's own module.json (process, claimed seat, addresses), the Dockerfile and Makefile pin test, the build-agent registry test and the manifest-in-use seat test move with their old package, as tests of mesh-sdk's exported API; a moved test is exempt from failing first.

2026-10-20 08:27:10 +00:00

jschoubben

66dc501fc4

Split the unit level from the integration level in cmd, builder, link, catalogue, inventory; cheap fixtures for the archive-entry bound, the registry waits and the catalogue copy (issue 895)

2026-10-17 21:32:23 +02:00

jochen

c9dd07f919

Never make a credential only a person can give, and give it once per provider (hq issue 164, ADR 0337)

mesh/merge-gate head c9dd07f919a2 merged into trunk 404b4409e70e — pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every …

Details

mesh/repo-check head c9dd07f919a2 merged into trunk 404b4409e70e — pass: its merge-check.sh passed (run 2)

Details

mesh/delivery delivered

Details

A Servarr app's API key, an indexer's key and a downloader's password are values the provider's
software holds; the pair path made a random value for every consumer of them, sealed it to both ends
and reported success, and the provider refused it. An offer may now say `"credential": {"issued-by":
"outside"}`: SecretFor never makes a value for it, the plan reads such a pair as given or not given
and sends the consumer no credential file until a person gives it, without refusing its machine;
remakeShared and SharedSecretFor never make a provider's own secret issued outside either.
`secret accept <provider's node> <provider module> <provision>` seals one value to every consumer that
binds the provision from that provider, the provider and the operator, under one generation; the
per-pair form is refused for such a provision, and rotate names the accept. A consumer may wait for a
provision's credential: the controller excuses the wait only when the store bears it out, and its
needs-operator condition names the one accept line.

Adds the replay of issue 164 (TestReplay164), written with only what the controller had before.

2026-10-13 11:37:31 +02:00