the spec names the resolver and the address #27

2026-09-25T21:51:37Z

jschoubben commented

2026-09-25 21:51:37 +00:00

Follow-up to #26, found on its first live deployment: dns and ip were declared, validated, and handed to the runtime — and part of no comparison, so every container compared equal and nothing was recreated, silently. Same shape as 04-ISSUES/045: a field not in the spec is a field that can never reach a container that already runs. Regression test proves both fields move the spec.

Follow-up to #26, found on its first live deployment: `dns` and `ip` were declared, validated, and handed to the runtime — and part of no comparison, so every container compared equal and nothing was recreated, silently. Same shape as 04-ISSUES/045: a field not in the spec is a field that can never reach a container that already runs. Regression test proves both fields move the spec.

jschoubben added 1 commit 2026-09-25 21:51:37 +00:00

the spec names the resolver and the address 260bf0b752

dns and ip were declared, validated, handed to the runtime — and part of
no comparison, so their first deployment compared every container equal
and changed nothing, silently. The same shape as 04-ISSUES/045: a field
that is not in the spec is a field that can never reach a container that
already runs.

jschoubben merged commit 5dbc8e5c3c into main

2026-09-25 21:51:42 +00:00

jschoubben deleted branch fix/the-spec-names-the-resolver-and-address

2026-09-25 21:51:42 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#27