Manual dashboard regenerate via msg.topic #41
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type: slice
Depends on: #36
Estimate: S (½ day)
Slice — layers touched
dashboardAPI commands registry → adapter (input handler) → log → integration test.
Context
Implements PRD F-12.
Scope
regenerate-dashboardto dashboardAPI'ssrc/commands/index.js.trigger: "manual"vstrigger: "deploy".Out of scope
Acceptance criteria
{{topic: "regenerate-dashboard"}}→ dashboardAPI logs a manual-trigger line and POSTs to Grafana.Slice #41 shipped on branch
slice/41-manual-regenBranches:
dashboardAPI·EVOLVWhat landed
recordChild/cachedChildSources) — used to remember registrations for later manual regen. By design, no persistence across restarts; cache rebuilds naturally as children re-register on next deploy.emitDashboardsFor) reused by bothchild.registerandregenerate-dashboard. Meta carriestrigger: 'child.register' | 'manual'for downstream filtering / dashboard tagging.regenerate-dashboardtopic (aliasregen) in the command registry.CONTRACT.mdupdated.Acceptance criteria (status)
{topic: "regenerate-dashboard"}→ dashboardAPI emits Grafana upsert messages for every cached child (no diff check). Verified byregenerate-dashboard re-emits for each cached child, bypassing diff.trigger: "manual"vstrigger: "child.register").Closes #41.