feat: expose infrastructure dependency inventory
Module Package Release / publish-packages (push) Successful in 12s

This commit is contained in:
2026-08-24 14:56:38 +02:00
parent b175658a0f
commit ac6b211827
9 changed files with 240 additions and 11 deletions
+12
View File
@@ -49,6 +49,18 @@ The Ops API reports:
- rendered PostgreSQL connection peak, declared server limit, and operator reserve
- recovery operation status, mode, checkpoint count, and last update
The separately authorized
`GET /api/v1/ops/infrastructure/dependencies` endpoint collects current,
module-owned infrastructure dependencies through the Core provider contract.
It is intended for the host deployer's destructive-change preflight, not for a
general data export. Results contain stable configuration references, lifecycle
states, scopes, numeric counts and required preparation actions; they never
contain credentials, tenant identifiers, file keys or secret-bearing endpoint
values. Ops itself contributes the current database, Redis coordination,
ingress, and load-balancing runtime bindings; feature modules contribute their
own persisted configuration and data. One unavailable or invalid provider makes the result incomplete, so a
caller must fail closed rather than treating missing provider data as zero.
These values are intentionally diagnostic. They do not replace deployment
configuration management, backups, monitoring, or restore drills.