docs(webui): the Triage settings comment says the host reads the stored route at its next admit, now that the host has a route (#1873, lane triage-wiring)

This commit was merged in pull request #1995.
This commit is contained in:
jason.woltje committed 2026-11-18 16:01:19 -06:00
1 parent c28ca57af6
commit 4a8d310cd5
1 file changed
+2 -1
+2 -1
View File
@@ -287,7 +287,8 @@ try {
const agentLevelRoutes = organizations ? [agentLevelsWriteRoutes({ configDir: configDir(), rolesDir: rolesDir(), trail })] : []; const agentLevelRoutes = organizations ? [agentLevelsWriteRoutes({ configDir: configDir(), rolesDir: rolesDir(), trail })] : [];
// #1873 triage-settings: Settings > Triage reads and saves the route store for the instance owner. // #1873 triage-settings: Settings > Triage reads and saves the route store for the instance owner.
// The model is checked against the catalogue each active organization's bus answers with, as an // The model is checked against the catalogue each active organization's bus answers with, as an
// organization's route change is. The Triage host above still gets route: null; saving starts nothing. // organization's route change is. Saving starts nothing: the Triage host above reads the store at its
// next admit.
const triageRoutes = system && (devOwner || ssoOn) ? [triageRouteRoutes({ const triageRoutes = system && (devOwner || ssoOn) ? [triageRouteRoutes({
dataRoot: system.dataRoot, log: line => console.log(line), dataRoot: system.dataRoot, log: line => console.log(line),
catalogues: async () => { catalogues: async () => {