Issue 161: an assignment does not record which provider answers it #210

2026-09-30T09:54:32Z

mesh-admin commented

2026-09-30 09:54:32 +00:00

ADR 0110 decided each assignment records where its requirements are answered
from; the control plane keeps only a per-machine pin (none recorded) and
resolves every requirement implicitly. Harmless with one provider; a second
one silently moves consumers' data.

ADR 0110 decided each assignment records where its requirements are answered from; the control plane keeps only a per-machine pin (none recorded) and resolves every requirement implicitly. Harmless with one provider; a second one silently moves consumers' data.

mesh-admin added 1 commit 2026-09-30 09:54:33 +00:00

Issue 161: an assignment does not record which provider answers it 39340fcd76

ADR 0110 decided each assignment records where its requirements are answered
from; the control plane keeps only a per-machine pin (none recorded) and
resolves every requirement implicitly. Harmless with one provider; a second
one silently moves consumers' data.

jschoubben added 2 commits 2026-09-30 11:28:24 +00:00

Merge remote-tracking branch 'origin/main' into issue/161-an-assignment-does-not-record-its-provider e8470057aa

Issue 163 (was 161): another record took 161 on main first 743051efe7

mesh-admin commented

2026-09-30 11:28:24 +00:00

Renumbered to 163: main gained its own 161 (and 162) while this was open.

Renumbered to **163**: main gained its own 161 (and 162) while this was open.

mesh-admin merged commit 76a535e69e into main

2026-10-01 09:24:07 +00:00

mesh-admin deleted branch issue/161-an-assignment-does-not-record-its-provider

2026-10-01 09:24:08 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#210