Files

master 2a25e7b2b0 feat(ui): reconnect registry-admin under integration hub [SPRINT-023]

Mount registry-admin routes under canonical /ops/integrations (and
/setup/integrations) with plans list, editor, and audit flows reachable
from integration-hub entry points.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-08 19:25:40 +02:00

1.6 KiB

Raw Permalink Blame History

Registry Admin Integration Route Reconnection

Module

Web

Status

IMPLEMENTED

Sprint

SPRINT_20260308_023_FE_unreachable_registry_admin_route

Description

Reconnected the disconnected registry-admin route family under the canonical integration hub. The registry-admin capability is mounted as a child of the integration shell, preserving integration-hub context and preventing a standalone product branch.

Canonical URL Contract

Accessible via both Ops and Setup parent paths:

/ops/integrations/registry-admin - Registry plan list (via Ops)
/setup/integrations/registry-admin - Registry plan list (via Setup)
.../registry-admin/plans - Plan list (explicit)
.../registry-admin/plans/new - Create plan
.../registry-admin/plans/:planId - Edit plan
.../registry-admin/audit - Audit trail

Implementation Details

Route file: src/Web/StellaOps.Web/src/app/features/integration-hub/integration-hub.routes.ts
- Added registry-admin child route with loadChildren before the catch-all :integrationId route
Feature routes updated:
- src/Web/StellaOps.Web/src/app/features/registry-admin/registry-admin.routes.ts - Added breadcrumb data, title, sprint ref
Tests: src/Web/StellaOps.Web/src/app/routes/integration-hub.routes.spec.ts

Key Decisions

Registry admin is treated as an integration-management capability, not a standalone product
Mounted before the catch-all :integrationId route to prevent path conflicts
Accessible from both /ops/integrations/ and /setup/integrations/ parent paths since integration-hub routes are shared
Navigation into registry-admin preserves the integration shell context

1.6 KiB Raw Permalink Blame History