stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 3 Releases Wiki Activity

chore(implplan): archive SPRINT_20260422_004 Concelier full connector control plane

Browse Source 
All 3 tasks DONE:
- CONN-CTRL-01 — Excititor provider management backend (commit 5c1b59580)
- CONN-CTRL-02 — CLI and Web control plane wiring (commit 387173276)
- CONN-CTRL-03 — Connector inventory docs and operator guidance (commit 387173276)

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
master
2026-04-22 19:29:11 +03:00
parent 3871732765
commit fe72e6d2f6
1 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

84
docs/implplan/SPRINT_20260422_004_Concelier_full_connector_control_plane.md
View File

@@ -1,84 +0,0 @@
# Sprint 20260422_004 - Concelier Full Connector Control Plane
## Topic & Scope
- Deliver a truthful connector control plane for advisory and VEX ingestion so operators can see what exists, what is runnable, and what is blocked.
- Add first-class Excititor provider management that matches the persisted provider store instead of relying on worker defaults or hidden configuration.
- Keep advisory sources and VEX providers split as separate operator surfaces, but link them through shared readiness semantics and documentation.
- Working directory: `src/Concelier/`.
- Expected evidence: targeted WebService tests, CLI verification, Web build/test evidence, and updated module docs.
## Dependencies & Concurrency
- Depends on the existing advisory source management surface in `StellaOps.Concelier.WebService`.
- Safe cross-module edits are allowed for `src/Cli/`, `src/Web/`, and `docs/**` when required to expose the new Excititor control plane.
- Do not broaden runtime state models; reuse persisted `IVexProviderStore` and `IVexConnectorStateRepository`.
## Documentation Prerequisites
- `docs/README.md`
- `docs/07_HIGH_LEVEL_ARCHITECTURE.md`
- `docs/modules/platform/architecture-overview.md`
- `docs/modules/concelier/architecture.md`
- `docs/modules/excititor/architecture.md`
- `docs/modules/concelier/operations/source-credentials.md`
- `src/Concelier/AGENTS.md`
## Delivery Tracker
### CONN-CTRL-01 - Excititor provider management backend
Status: DONE
Dependency: none
Owners: Developer / Implementer
Task description:
- Add first-class Excititor provider management contracts and endpoints in `src/Concelier/` that expose the persisted provider catalog, runtime readiness, enable or disable intent, and operator-safe execution controls.
- The backend must report truthful status for built-in and persisted providers using shared readiness concepts (`ready`, `blocked`, `disabled`, `planned`) and must not create a second source of truth outside the existing Excititor persistence layer.
Completion criteria:
- [x] Excititor WebService exposes provider catalog and status endpoints backed by persisted provider state.
- [x] Enable, disable, and run actions exist for provider entries and preserve truthful blocked states when configuration is incomplete.
- [x] Targeted backend tests cover the new provider control-plane behavior.
### CONN-CTRL-02 - CLI and Web control plane wiring
Status: DONE
Dependency: CONN-CTRL-01
Owners: Developer / Implementer
Task description:
- Extend the CLI and Web UI so operators can inspect and manage VEX providers without environment variables.
- Keep the VEX provider surface separate from advisory source management, but link the navigation and terminology so operators can move between both views.
Completion criteria:
- [x] CLI exposes Excititor provider inspection and control actions against the new backend API.
- [x] Web UI exposes a linked VEX provider management view with truthful readiness and operator actions.
- [x] Existing advisory source flows remain intact.
### CONN-CTRL-03 - Connector inventory docs and operator guidance
Status: DONE
Dependency: CONN-CTRL-02
Owners: Documentation author / Developer / Implementer
Task description:
- Update Concelier and Excititor docs to describe the full connector inventory, the split-but-linked operator model, credential entry paths, and blocked or sleeping behavior for connectors that require credentials.
- Record implementation decisions, evidence, and any remaining catalog-to-runtime gaps.
Completion criteria:
- [x] Docs under `docs/modules/concelier/` and `docs/modules/excititor/` describe inventory, readiness semantics, and operator workflows.
- [x] Sprint `Execution Log` and `Decisions & Risks` link to the updated docs and test evidence.
- [x] Any remaining unsupported connectors are documented as planned rather than implied to be working.
## Execution Log
| Date (UTC) | Update | Owner |
| --- | --- | --- |
| 2026-04-22 | Sprint created. Began Excititor provider control-plane implementation using the persisted provider store and connector state repositories as the single runtime truth. | Developer |
| 2026-04-22 | Added `/excititor/providers` list, detail, update, enable, disable, and run endpoints plus targeted provider-management tests. `scripts/test-targeted-xunit.ps1` passed for `StellaOps.Excititor.WebService.Tests.ProviderManagementEndpointsTests` with 5 tests run and 0 failures. | Developer |
| 2026-04-22 | Wired CLI provider verbs and the linked Web VEX provider management page. `npx vitest run --config vitest.codex.config.ts src/app/features/integrations/advisory-vex-sources/advisory-vex-route-helpers.spec.ts` passed and `npx ng build --configuration development` passed. | Developer |
| 2026-04-22 | Updated connector inventory and Excititor provider control-plane docs to reflect the 78-source advisory catalog, 31 built-in runnable advisory pipelines, seven VEX provider IDs, and the remaining host-config-only credential gaps on the VEX side. | Developer |
## Decisions & Risks
- Decision: advisory sources and VEX providers remain separate operator surfaces, but they will share readiness language and linked navigation so the control plane stays truthful without flattening different runtimes into one fake catalog.
- Decision: credential-gated connectors must preserve operator enable intent while reporting `blocked` readiness until stored configuration is supplied through supported UI or CLI paths.
- Decision: the advisory catalog inventory is now documented from source-of-truth registries instead of stale module summaries. See `docs/modules/concelier/connectors.md` and `docs/modules/excititor/operations/provider-control-plane.md`.
- Risk: the Concelier advisory catalog is broader than the current runnable host surface, and Excititor currently has worker-seeded defaults but no WebService control plane. Docs and APIs must distinguish catalog breadth from tested runtime support to avoid false claims.
- Risk: Web routing already contains advisory-oriented feature naming. Adding VEX management without duplicating large UI components may require targeted refactoring in `src/Web/`.
- Risk: Excititor provider metadata can now be managed via UI and CLI, but secret-bearing connector settings for `excititor:msrc`, `excititor:suse-rancher`, `excititor:oci-openvex`, and optional Cisco VEX auth remain host-config-only. The provider control plane surfaces this truth as `planned` or `blocked` instead of claiming end-to-end credential parity that does not yet exist.
## Next Checkpoints
- Backend provider endpoints and tests passing.
- CLI and Web provider management wired to the new endpoints.
- Module docs updated with evidence links and remaining planned gaps.