feat: reconcile the broker before the engine (NetOrk/netork#1308)
CI / check (pull_request) Failing after 2m28s

redis was in no list: the engine is recreated with --no-deps, and the
infrastructure reconcile left databases out on purpose. A changed definition
-- Valkey in place of redis:7-alpine -- therefore never reached a host.

The broker is now brought up with a plain `up -d --wait` right before the
engine is recreated: recreated only when its definition changed, so an
unchanged broker keeps running and keeps its queue, and the engine comes up
against a healthy broker. If the broker does not get healthy within 120 s, the
deploy stops with the old engine still running.
This commit is contained in:
Christian Manivong committed 2026-10-20 22:26:25 +02:00
1 parent c1b1eb07b9
commit 7e4fff8025
3 files changed
+102 -5

No files matched your search

+3 -3
View File
@@ -76,9 +76,9 @@ def test_every_up_sees_the_version_being_deployed(tmp_path: Path) -> None:
assert result.returncode == 0, result.stderr
seen = (tmp_path / "env-at-up").read_text().splitlines()
# The engine services' recreate, then the infrastructure reconcile.
assert len(seen) == 2, seen
assert seen == ["NETORK_VERSION=latest-dev"] * 2, (
# The broker, the engine services' recreate, then the infrastructure reconcile.
assert len(seen) == 3, seen
assert seen == ["NETORK_VERSION=latest-dev"] * 3, (
"a container was started while .env still named the previous deploy's version"
)