Resync hq ADR references 0044-0054 -> 0039-0049 after the hq record reconciliation
This commit is contained in:
@@ -1,4 +1,4 @@
|
||||
// Node-RED's admin-API client — nodered's own code, living in the module (novox/hq ADR 0044). Only
|
||||
// Node-RED's admin-API client — nodered's own code, living in the module (novox/hq ADR 0039). Only
|
||||
// this module's tools import it; nodered has nothing to poll, so there is no events entrypoint.
|
||||
//
|
||||
// Node-RED exposes a runtime admin API under its base URL: GET/POST /flows for the whole flow
|
||||
@@ -20,7 +20,7 @@ export interface NodeRedNodeModule {
|
||||
types: string[];
|
||||
}
|
||||
|
||||
/** The settings-merged config the mesh delivers (novox/hq ADR 0051): { url, apiKey, token, password, user, ... }. */
|
||||
/** The settings-merged config the mesh delivers (novox/hq ADR 0046): { url, apiKey, token, password, user, ... }. */
|
||||
function meshConfig(file?: string): Record<string, string> {
|
||||
if (!file) return {};
|
||||
try { return JSON.parse(readFileSync(file, "utf8")) as Record<string, string>; }
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
{
|
||||
"name": "@novox/module-nodered",
|
||||
"version": "0.1.0",
|
||||
"description": "nodered — flow-based automation. Its client and tools live here (novox/hq ADR 0044).",
|
||||
"description": "nodered — flow-based automation. Its client and tools live here (novox/hq ADR 0039).",
|
||||
"type": "module",
|
||||
"private": true,
|
||||
"dependencies": {
|
||||
|
||||
@@ -1,7 +1,7 @@
|
||||
// nodered's tools — importing nodered's own admin-API client (novox/hq ADR 0044). They return
|
||||
// nodered's tools — importing nodered's own admin-API client (novox/hq ADR 0039). They return
|
||||
// structured data; the mesh serves them through the sdk's tool harness.
|
||||
//
|
||||
// The deploy tool is nodered's one event source (novox/hq ADR 0046/0047): a successful deploy
|
||||
// The deploy tool is nodered's one event source (novox/hq ADR 0041/0042): a successful deploy
|
||||
// emits module.nodered.flows.deployed. nodered has nothing to observe on a timer, so there is no
|
||||
// separate events entrypoint — the emit rides the action that causes it. The emit is best-effort:
|
||||
// if no broker is bound, the deploy still succeeds and the announcement is simply skipped.
|
||||
|
||||
Reference in New Issue
Block a user