11 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	98ca97fc5b	Verify the bus's snapshot with a tool, sharing the snapshot program's archive code (issue 1842) ... The upgrade and restore steps told a person to docker exec the snapshot program; no mesh tool did it. nats_snapshot_verify reads the newest bus.tar of the snapshots directory only.	2026-10-22 14:24:25 +02:00
jschoubben	c948f3a61c	Skip the bus's docker tests loudly where there is no docker, and run them by name in a docker step of the merge check where there is (ADR 0480 clause 6)	2026-10-22 10:18:15 +02:00
jschoubben	91877e3421	Put the bus's two mounted programs under a directory the module declares, as the controller's module check requires (review round 1, C1)	2026-10-22 10:04:31 +02:00
jschoubben	77b89ff182	Take the rehearsal tool out of the nats module: a new nats build is held until the bus upgrade itself, so it could only run after the step it rehearses (ADR 0236 section 36)	2026-10-22 10:01:23 +02:00
jschoubben	e7ca330e1f	Rehearse the bus upgrade on a copy of the last snapshot with a tool of the nats module, and run the docker tests only as integration tests (issue 1642, ADR 0480 clause 6)	2026-10-22 10:00:15 +02:00
jschoubben	b4e90e5fce	Run the bus from its pinned upstream image with the snapshot program and the entrypoint mounted, and write and rehearse the way there and back (issues 1640, 1641, 1642, ADR 0480 clauses 1-3, 5, 6, 11)	2026-10-22 09:55:03 +02:00
jschoubben	4fdb047cc8	nats: say whether a user's grant is in force on the running server, not only written (hq issue 353) ... nats_user_can read the user list on the machine. A list written is not a list the bus enforces until the server reloads it: on 2026-10-09 the controller asked between the write and the reload's effect. The answer now carries in_force — allowed in the file, and the server's config_load_time after the file's write — with why when it is not, and anything not known is not in force.	2026-10-12 12:13:03 +02:00
jochen	ea69e795ab	Read the tested nats release from the server itself ... The build seat's test binary listed no dependencies, so the check that the image and the tests run one release failed on a release that matched.	2026-10-08 18:07:29 +02:00
jochen	0063cc2ad1	Say who opens and closes connections to the bus, and why each closed (hq issue 327) ... The connection total rose by hundreds an hour while the open count stayed flat, and nothing could say which clients those were.	2026-10-08 17:54:01 +02:00
jochen	0275c2eeac	nats: run 2.11.17, which hands a consumer with several filters every message (hq issue 266) ... On 2.10.29 such a consumer was moved past a message now and then without handing it over; the controller's events consumer has seven filters, and a merge on the stream never reached it. The test reproduces the skip on 2.10.29 and keeps the image's release equal to the server it tests.	2026-10-06 01:29:20 +02:00
jochen	f53fc0929b	The bus's own tools: server, connections, subscriptions, streams, backlog, buckets, users, user_can ... A Go bundle the runtime launches beside the nats module's server. It reads the server's monitoring API and the composed user list — never a password hash — and changes nothing. Reached directly when the endpoint is published, through the container otherwise: its configuration binds monitoring to the container's own loopback, so the published port answers nothing today.	2026-10-04 16:51:33 +02:00