From 4f981cc2d7a513ac2672bff5b78e2b85202ab005 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 6 Oct 2026 15:02:18 +0200 Subject: [PATCH] ADR 0226: say a retired definition is not ADR 0230's retired consumer The two retirements are easy to confuse; the second deletes nothing a person must approve. --- ...-by-its-own-name-and-the-proxy-names-its-public-issuer.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/02-DECISIONS/0226-the-private-network-is-assigned-by-its-own-name-and-the-proxy-names-its-public-issuer.md b/02-DECISIONS/0226-the-private-network-is-assigned-by-its-own-name-and-the-proxy-names-its-public-issuer.md index 6d0973a..aa342c1 100644 --- a/02-DECISIONS/0226-the-private-network-is-assigned-by-its-own-name-and-the-proxy-names-its-public-issuer.md +++ b/02-DECISIONS/0226-the-private-network-is-assigned-by-its-own-name-and-the-proxy-names-its-public-issuer.md @@ -84,7 +84,10 @@ catalogue no longer holds one. machine.** `module forget` refuses a module the controller ships, because the next start would put it back; so a retired one could be removed by nothing. At start the controller removes every module it recorded as its own and no longer ships — unless a machine is still assigned it, or the mesh still -holds settings, secrets or ports for it, in which case it is kept and the start says why. +holds settings, secrets or ports for it, in which case it is kept and the start says why. This removes +a module's *definition* from the catalogue, never a consumer's data: what a consumer leaves behind is +[ADR 0230](0230-a-consumer-the-mesh-stops-asking-for-is-retired-and-deleted-only-by-a-person.md)'s, and +a module holding anything is never removed here. **3. The proxy names its public issuer.** `route-proxy` no longer requires `acme-ca`; its `acme.env` states Let's Encrypt's production directory exactly as the binding rendered it. `public-acme` leaves