From b8d8101c454e1a5b7b2401d161554f64cb645642 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 1 Oct 2026 12:14:49 +0200 Subject: [PATCH 1/2] =?UTF-8?q?Issue=20180:=20the=20live=20rotation=20done?= =?UTF-8?q?=20=E2=80=94=20searxng's=20secret=20on=20the=20home=20server=20?= =?UTF-8?q?through=20the=20console?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- .../00-report.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/04-ISSUES/180-a-modules-own-secret-cannot-be-rotated/00-report.md b/04-ISSUES/180-a-modules-own-secret-cannot-be-rotated/00-report.md index 07ef9fa..5b91167 100644 --- a/04-ISSUES/180-a-modules-own-secret-cannot-be-rotated/00-report.md +++ b/04-ISSUES/180-a-modules-own-secret-cannot-be-rotated/00-report.md @@ -55,6 +55,17 @@ rotates a secret taken at start, refuses an applied one, an undeclared one, an a unknown name, each in its own words; the verb's two shapes; and, live, a secret rotated through the console on a module that reads it at start, the module restarted, and the module working. +*Done live, 2026-10-01 10:13 UTC:* the search module on the home server, the first definition to say +`taken: at-start` whose value the mesh had made. Asked through the console; the controller said it was +rotated and sent the machine; twenty-seven seconds later the secret file carried a new write time, the +server container had restarted on it, and the module answered. The two secrets filed in the forge's +report, the automation module's token and admin password, were refused: both had been accepted by hand +during adoption, and that refusal is the one ADR 0113 asks for — something outside the mesh may hold +an accepted value, so replacing it is a person's act. Modules whose source is pinned to a commit are +not rebuilt by a merge; their new definition was registered by asking for a build of main through the +console, which since [issue 176](../176-the-consoles-build-tool-neither-waits-nor-registers/00-report.md) +registers what it hears. + ## Open — the applied form The staged rotation ADR 0114 decided for an applied secret is not built: the vault delivering the -- 2.54.0 From e00e3bc3ce11acf6d2b37cb57417d48432ca49f8 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 1 Oct 2026 12:15:31 +0200 Subject: [PATCH 2/2] Issue 181 (was 163, was 161): two records answered to 163; renumbered to the next free number across main and open pull requests --- .../00-report.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename 04-ISSUES/{163-an-assignment-does-not-record-which-provider-answers-it => 181-an-assignment-does-not-record-which-provider-answers-it}/00-report.md (97%) diff --git a/04-ISSUES/163-an-assignment-does-not-record-which-provider-answers-it/00-report.md b/04-ISSUES/181-an-assignment-does-not-record-which-provider-answers-it/00-report.md similarity index 97% rename from 04-ISSUES/163-an-assignment-does-not-record-which-provider-answers-it/00-report.md rename to 04-ISSUES/181-an-assignment-does-not-record-which-provider-answers-it/00-report.md index f9770f7..c05d7b6 100644 --- a/04-ISSUES/163-an-assignment-does-not-record-which-provider-answers-it/00-report.md +++ b/04-ISSUES/181-an-assignment-does-not-record-which-provider-answers-it/00-report.md @@ -8,7 +8,7 @@ fixed-by: amended-design: --- -# 163 — An assignment does not record which provider answers it +# 181 — An assignment does not record which provider answers it ## What was observed -- 2.54.0