lavinmq-bed: prove the AMQP provider provisions a require-only consumer #13

2026-09-06T21:21:20Z

jschoubben commented

2026-09-06 21:21:20 +00:00

Two-node bed: substrate broker on anchor, lavinmq provider + amqp-ping consumer on laptop (the 5672 collision twin of two-node-db's 5432). The consumer gets its scoped vhost+user, connects, and round-trips a message. Drove out — and now proves the fix for — the require-only-mint bug (mesh-control). SUITE_EXIT=0.

https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

Two-node bed: substrate broker on anchor, lavinmq provider + amqp-ping consumer on laptop (the 5672 collision twin of two-node-db's 5432). The consumer gets its scoped vhost+user, connects, and round-trips a message. Drove out — and now proves the fix for — the require-only-mint bug (mesh-control). **SUITE_EXIT=0.** https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

jschoubben added 3 commits 2026-09-06 21:21:20 +00:00

Add lavinmq-bed: a two-node amqp provider + consumer bed 8e494c0e78

A lavinmq provider and an amqp-ping consumer ride laptop while the
substrate's own broker owns 5672 on anchor — the twin of two-node-db.
lavinmq is the mesh's control broker AND a user-facing capability, so a
provider must publish 5672 for its consumers and cannot share a node
with the control broker that already owns it; the split unblocks the
chain single-node.

The bed proves, layered: the run-once bootstrap computed the admin hash
and wrote the broker config before the broker started (ADR 0052); the
service and both runtimes are up and stable; each module got its scoped
broker account on the substrate broker; the provisioner created the
consumer's vhost AND user, both named for the derived login; and the
consumer connected to that vhost with the mesh-minted password and
round-tripped a message. The consumer uses ${bound:amqp:as} for user
and vhost both, and the provider's serves carries the port.

Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

lavinmq-bed: reproduces a credential-mint gap for require-only consumers of a parameterless provision 73bd086193

The lavinmq AMQP provider comes up and serves, but its receives file has given:[] — the
consumer amqp-ping (requires amqp, contributes nothing, as a parameterless provision like
redis-cache takes no per-consumer payload) is never minted a credential, so the provisioner
creates no vhost. Diagnostic in the test dumps the empty grants file + the provisioner log.
This is the resolve/plan mint path (grantsFor -> SecretsFrom), ADR 0048 territory, and it
likely affects redis-cache consumers the same way. Preserved for a focused fix; not merged.

Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

lavinmq-bed: GREEN — AMQP provider provisions a require-only consumer's vhost (mint fix) f04c4ba3be

Two-node: substrate broker on anchor, lavinmq provider + amqp-ping consumer on laptop. The
consumer gets its scoped vhost+user, connects, and round-trips a message. Requires the
mesh-control require-only-mint fix. Diagnostic removed now it's green. SUITE_EXIT=0.

Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF

jschoubben merged commit 0a132aa00e into main

2026-09-06 21:21:49 +00:00

jschoubben deleted branch feat/lavinmq-bed

2026-09-06 21:21:49 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#13