Run the forge, on a database the mesh gave it

Everything up to now stopped at composing a declaration. That proves the
control plane and the host agree, and proves nothing about whether the
thing described works — which is how five modules sat pinned to images
that did not exist while parsing and resolving perfectly.

The forge is the right one to run first. It needs a database from
another module, a password it did not choose, and a connection string it
could not have written itself: the address and port come from what the
database serves, the user name from what the mesh decided both ends
would call it. If any of that is wrong it cannot start, and nothing else
in this suite would notice.

The test checks the chain in the order it has to happen — the login
exists, the database it owns exists, the forge answers, and its log does
not say authentication failed. That last one matters: a forge that
started and could not reach its database would still answer on its port.

Rewriting image references is now shared rather than copied from the
bundle, which had the same problem first. A digest is not knowable until
something is built, and when it is, it belongs to whichever registry
served it — so the text says which image and the scenario says which
copy. Matching is on the repository, with a test that a repository
ending in another one is not half-replaced.

Also makes the planning test put the machine back. Tests here share one
mesh, so the five modules it assigned were inherited by whatever ran
next; harmless while nothing pushed, and not harmless now.

This commit is contained in:

jschoubben

2026-09-01 15:39:30 +02:00

parent bb14ecb7e0

commit 55022edc1e

4 changed files with 205 additions and 0 deletions

									
										scenarios/two-nodes.yml
									
		+4
		
												View File
												
				@@ -40,6 +40,10 @@ images:

				  - mesh-provision-postgres:development

				  # And the proxy, which is what turns a route grant into traffic actually arriving.

				  - mesh-route-proxy:development

				  # And a forge, so one of the real module descriptions can be started rather than only planned.

				  # It is the first of them to run: it needs a database from another module, a credential it did

				  # not choose, and a connection string it could not have written itself.

				  - gitea/gitea:1.22

				place:

				  all: [host, runtime]