Keep builds in the builds bucket and move the build rows there at start (issue 1090)

Once chain_moved records the kind, RecordBuild and every build read go through the chain (reuse key and published added); before that the tables are read as before. The serving controller copies the rows at its start, holding the lease: idempotent per key, rows counted against keys, the largest value measured, a refusal (urgent condition, nothing switched) on a count that differs or a value over the bus's largest, and a re-read when the table took a row meanwhile. ForTest attaches the chain in memory with builds moved; ForTestBefore leaves it unmoved. Build requests, gates and the other kinds are still in their tables.
2026-10-18 02:49:51 +02:00
parent 36c4ce605e
commit f89d870308
20 changed files with 1790 additions and 90 deletions
@@ -139,3 +139,9 @@
 ./cmd/mesh-controller TestADeliveryGroupMovingAModuleMachinesRunPassesTheGate
 ./cmd/mesh-controller TestAModuleMovesOnTheOperatorsApproveOfTheMergeThatMovedIt
 ./cmd/mesh-controller TestAModuleBuiltFromANewRepositoryIsRegisteredOnlyOnTheOperatorsApproveOnTheBus
+./internal/inventory TestTheMoveCopiesTheBuildRowsAndAgainWritesNothing
+./internal/inventory TestAControllerRestartedMidMoveFinishesItAndOverwritesNothing
+./internal/inventory TestTheMoveRefusesAValueOverTheLargestMessage
+./internal/inventory TestTheMoveRefusesOnACountThatDiffers
+./internal/inventory TestTheMoveWithoutTheLeaseWritesNothing
+./internal/inventory TestBuildsOnTheBusAreReadBackByEveryReader