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
jschoubben