Ingestion Health — Wire ConnectorConfigReader runtimeEnabled to RuntimeConfigResolver

[mareklibra]

Labels: ready-to-code (when starting), workspace/boost, feature
Depends on: #4044 (connector leaf keys registered in boostConfigFields)
Unblocks: correct health enabled / ?includeDisabled under DB overrides; soft prerequisite for connector admin UX that relies on health reflecting runtime toggles
RHIDP / Feature: RHDHPLAN-1513 — follows #4043 handoff contract
Parent gate: #4044 implementation gate (OUT → this issue)

Why (single scope)

#4250 introduced ConnectorConfigReader reading both enabled flags from YAML/ConfigApi only. After #4044, boost.connectors.<id>.enabled is db-overridable via RuntimeConfigResolver, but health still ignores DB overrides until this handoff.

listCandidates() is synchronous today; RuntimeConfigResolver.resolve() is async — this issue owns that API change and health call-site updates. Keep it out of #4044 so the schema PR stays small.

In

• Inject RuntimeConfigResolver into ConnectorConfigReader (startup flag stays YAML/ConfigApi).
• runtimeEnabled ← await resolver.resolve('boost.connectors.<id>.enabled') with default true when unset.
• Make discovery async (listCandidates(): Promise<…> or equivalent) and update HealthStatusService / routes / tests.
• Tests:
  • YAML-only runtime enabled (regression)
  • DB override enabled: false → candidate runtimeEnabled: false (and health filter behavior)
  • Startup-disabled providers still excluded even with includeDisabled=true

Out

• Registering connector Zod leaves (Connector Config — Zod Schemas and RuntimeConfigResolver Extension (issue 6 of 29) #4044)
• Provider hot-reload (Hot-Reload Propagation to Active Connectors (issue 22 of 29) #4060)
• Admin UI / admin config HTTP API (Connector Config Admin UI (issue 28 of 29) #4066)
• Schema migration / __schemaVersion

Specs / refs

• #4043 implementation gate — “Contract Connector Config — Zod Schemas and RuntimeConfigResolver Extension (issue 6 of 29) #4044 must preserve / complete”
• plugins/boost-backend/src/ingestion/ConnectorConfigReader.ts
• openspec/changes/connector-config-hot-reload/design.md (namespace table)

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:07 AM UTC · Completed 8:10 AM UTC

Commit: ff6683f · View workflow run →

[fullsend-ai-triage]

This issue is blocked on #4044 (Connector Config — Zod Schemas and RuntimeConfigResolver Extension), which is still open with no PRs in flight. #4044 must land first so that boost.connectors.<id>.enabled is registered as a db-overridable leaf key in RuntimeConfigResolver — without that registration, there is nothing for ConnectorConfigReader to resolve against.

Once #4044 merges, this issue is well-scoped and ready to implement: inject RuntimeConfigResolver, make listCandidates() async, and update HealthStatusService / routes / tests accordingly.

Blocked by:

• Connector Config — Zod Schemas and RuntimeConfigResolver Extension (issue 6 of 29) #4044

---

Labels: Issue is a feature request in the boost workspace, currently blocked on prerequisite #4044.