Ingestion Health Admin UI and Disconnected-Cluster View (issue 26 of 29)

[gabemontero]

Labels: ready-to-code
Depends on: Issue 3 (#4041 — defines ai-catalog.admin permission), Issue 5 (#4043 — health API, error classification)
RHIDP Stories: RHIDP-15336, RHIDP-15339
Feature: RHDHPLAN-1513 — Epic RHIDP-15331

Implement IngestionHealthPanel.tsx with per-connector health cards (PatternFly Card/Label), status badges (healthy/degraded/failing/disabled), timestamps, error summaries with diagnostic guidance, "Force Sync" buttons, disabled connector visual treatment (grey badge, no error indicators), disconnected-cluster differentiation, and health data polling via useSWR with 30s refresh. Includes Force Sync backend routes, connector provider integration, and RBAC gating for the health API endpoint (deferred from Issue 5).

Tasks

Deferred from Issue 5 (RHIDP-15335 — health API RBAC gating):

• 2.5 Implement RBAC gating via ai-catalog.admin permission check in GET /api/boost/ingestion-health route handler (using permissions.authorize())

From openspec/changes/ingestion-health-dashboard/tasks.md group 4 (RHIDP-15336, RHIDP-15339):

• 4.1 Create IngestionHealthPanel.tsx component
• 4.2 Implement health card rendering with PatternFly components
• 4.3 Add status badge rendering (success/warning/danger/outline variants)
• 4.4 Add timestamp rendering with react-time-ago
• 4.5 Add sync metrics display
• 4.6 Add error summary section with diagnostic guidance
• 4.7 Add "Force Sync" button with disabled state during run
• 4.8 Implement disabled connector visual treatment (RHIDP-15339)
• 4.9 Add loading state
• 4.10 Add error state
• 4.11 Add empty state
• 4.12 Implement health data polling via useSWR with 30s refresh
• 4.13 Add responsive grid layout (PatternFly Gallery)

From openspec/changes/ingestion-health-dashboard/tasks.md group 6 (RHIDP-15335, RHIDP-15336):

• 6.1 Implement POST /api/boost/ingestion-health/:connectorId/force-sync route
• 6.2 Add connector run state registry
• 6.3 Implement concurrent Force Sync prevention (409 if already running)
• 6.4 Implement Force Sync trigger
• 6.5 Add Force Sync timeout wrapper
• 6.6 Implement status polling route
• 6.7 Add Force Sync UI polling
• 6.8 Add Force Sync error handling in UI
• 6.9 Add Force Sync integration tests

From openspec/changes/ingestion-health-dashboard/tasks.md group 7:

• 7.1–7.6 Connector provider integration (health tracking hooks in GitHub/GitLab/Jira providers, sync metrics, error capture)

From openspec/changes/ingestion-health-dashboard/tasks.md group 8:

• 8.1–8.4 Navigation integration (sidebar item, route, active state highlighting, pattern consistency)

Specifications

• openspec/changes/ingestion-health-dashboard/specs/admin-health-ui/spec.md

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:04 PM UTC · Completed 8:06 PM UTC
Commit: e03b281 · View workflow run →

[fullsend-ai-triage]

This issue depends on #4043 (Ingestion Health — API, Data Model, Error Classification), which is still open with no PRs in progress.

The IngestionHealthPanel.tsx component specified here needs to poll the GET /api/boost/ingestion-health endpoint and consume the health status data model (healthy/degraded/failing/unknown status derivation, boost_sync_attempts table, SyncAttemptsRepository) — all of which are defined and implemented in #4043. The Force Sync backend routes (task group 6) also depend on the connector run state registry and sync infrastructure from #4043.

Until #4043 lands, work on this issue would have no backend API to integrate against. Marking as blocked on that prerequisite.

Blocked by:

• Ingestion Health — API, Data Model, Error Classification (issue 5 of 29) #4043

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:26 PM UTC · Completed 8:28 PM UTC
Commit: f089b0c · View workflow run →

[fullsend-ai-triage]

Triage: Blocked on prerequisites

This issue remains blocked on two open dependencies, both with no PRs in progress:

1. Ingestion Health — API, Data Model, Error Classification (issue 5 of 29) #4043 — Ingestion Health API, Data Model, Error Classification (previously identified): The IngestionHealthPanel.tsx component needs to poll GET /api/boost/ingestion-health and consume the health status data model (healthy/degraded/failing/unknown derivation, boost_sync_attempts table, SyncAttemptsRepository). The Force Sync backend routes (task group 6) also depend on the connector run state registry and sync infrastructure defined there.

2. AI Catalog Permissions, Backend Enforcement, Conditional Rules (issue 3 of 29) #4041 — AI Catalog Permissions, Backend Enforcement (newly identified): Task 2.5 requires RBAC gating via the ai-catalog.admin permission check in the health API route handler using permissions.authorize(). That permission is defined and implemented in AI Catalog Permissions, Backend Enforcement, Conditional Rules (issue 3 of 29) #4041.

Until both prerequisites land, meaningful work on this issue cannot proceed.

Blocked by:

• Ingestion Health — API, Data Model, Error Classification (issue 5 of 29) #4043
• AI Catalog Permissions, Backend Enforcement, Conditional Rules (issue 3 of 29) #4041

Blocked by:

• Ingestion Health — API, Data Model, Error Classification (issue 5 of 29) #4043
• AI Catalog Permissions, Backend Enforcement, Conditional Rules (issue 3 of 29) #4041