Commit Graph
9 Commits
Author SHA1 Message Date
jschoubben 5ea88b149b The three modules name their base rather than pinning a copy of it
Each named a digest produced inside a lab that no longer exists, so none of them
could be built anywhere else. They say which module they stand on now, and there
is deliberately no default — a build nobody told stops at the declaration rather
than at a reference that resolves to nothing.
2026-09-13 23:53:22 +02:00
jschoubben 729582cc55 Remove what was only there to move a commit
A line in postgres's recipe and a one-line file in amqp-ping, both added to
move a commit and watch the mesh notice. The proofs worked; neither was meant
to stay. MESH_MODULE is set from the sealed credential at run time anyway, so
baking it in was dead weight as well as noise.
2026-09-13 11:15:33 +02:00
jschoubben 87243bc524 Every module stands on a base the mesh built
The base was a digest typed in by hand, for an image nothing in the mesh could
produce — so the graph held edges pointing at it with no version on the far end,
and the one change that reaches every module at once could never be noticed.
It is a module now, and these edges resolve.
2026-09-13 02:45:37 +02:00
jschoubben 1d0d9a3894 Name the module in its own runtime, and move the artifact with it 2026-09-13 01:58:48 +02:00
jschoubben 358c7d5a2d Move postgres's commit, to watch the mesh roll it out by itself 2026-09-13 01:57:00 +02:00
jschoubben c774d5dbe0 Install the postgres client the way the runtime base can
The published base is debian; apk is not there and the build said so.
2026-09-13 01:28:15 +02:00
jschoubben 6ebf51d312 postgres's runtime carries the client it provisions through
Its provisioner runs DDL by shelling out to psql, which the runtime base has no
reason to hold. Every create failed with ENOENT and retried for ever.
2026-09-13 01:26:23 +02:00
jschoubben e742b6a569 The catalogue builds its own runtime, and postgres serves its tools
Both modules keep their tools in an entrypoint of their own, so an image that
named only the consumer would serve none of them.
2026-09-13 01:13:43 +02:00
jschoubben d6c9c8d666 postgres builds its own runtime, like any other module
Its provisioner container named an image nobody could produce — a zero digest
placeholder. It names an artifact instead, and the module says how to build it,
so the mesh can make the database provider the catalogue needs.
2026-09-13 01:10:45 +02:00