From 6b0164c2ba975f415dad5c9a5d57f0a2efa76172 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 1 Oct 2026 11:44:29 +0200 Subject: [PATCH] nodered says it reads its API token and admin password at start, so the mesh may rotate them (hq 180) Both land in settings.js and the runtime's config file, and the containers that read them restart on those files; a rotation is a new value and a restart. The broker credential says nothing yet: its other party is the bus, and that rotation is the two-party form. --- modules/nodered/module.json | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/modules/nodered/module.json b/modules/nodered/module.json index 595c961..0ce746a 100644 --- a/modules/nodered/module.json +++ b/modules/nodered/module.json @@ -5,8 +5,14 @@ "flows.deployed" ], "own-secrets": { - "admin": "${dir:mesh-state}/admin", - "api-token": "${dir:mesh-state}/api-token", + "admin": { + "path": "${dir:mesh-state}/admin", + "taken": "at-start" + }, + "api-token": { + "path": "${dir:mesh-state}/api-token", + "taken": "at-start" + }, "broker": "${dir:mesh-state}/broker" }, "capabilities": [ -- 2.54.0