stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 14 Releases Wiki Activity
Files
f43e828b4e21957636ce35cdaf50bb29da5d4e1d
git.stella-ops.org/docs/modules/policy/prep/2025-11-22-export-console-23-001-prep.md
StellaOps Bot f43e828b4e
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details
feat: Implement MongoDB orchestrator storage with registry, commands, and heartbeats 
- Added NullAdvisoryObservationEventTransport for handling advisory observation events.
- Created IOrchestratorRegistryStore interface for orchestrator registry operations.
- Implemented MongoOrchestratorRegistryStore for MongoDB interactions with orchestrator data.
- Defined OrchestratorCommandDocument and OrchestratorCommandRecord for command handling.
- Added OrchestratorHeartbeatDocument and OrchestratorHeartbeatRecord for heartbeat tracking.
- Created OrchestratorRegistryDocument and OrchestratorRegistryRecord for registry management.
- Developed tests for orchestrator collections migration and MongoOrchestratorRegistryStore functionality.
- Introduced AirgapImportRequest and AirgapImportValidator for air-gapped VEX bundle imports.
- Added incident mode rules sample JSON for notifier configuration.
2025-11-22 12:35:38 +02:00

1.4 KiB
Raw Blame History

Policy Export · Console 23-001 Prep

Status: Ready for implementation (2025-11-22) Owners: Policy Guild · Scheduler Guild · Observability Guild Scope: Define the export bundle + scheduler job surface needed for Console export task 23-001.

Export Bundle Contract

  • Payload: NDJSON of advisory and VEX observations filtered by tenant + product set; include provenance block with source, fetchedAt, digest, evidenceBundleId.
  • Envelope: bundleId, createdAt, policyHash, schemaVersion, itemsSha256, optional transparency entry.
  • Determinism: sort items by observationId; timestamps truncated to seconds; hashes sha256 lower-case hex.

Scheduler Job Shape

  • jobType: console-export with fields tenantId, bundleId, filters, destinationUri (file:// or s3://), retryPolicy, notificationChannel.
  • Status transitions: queued → running → completed/failed; progress fields exportedCount, failedCount.
  • Observability: metrics policy_console_export_jobs_total{status}, policy_console_export_duration_seconds, logs with bundleId and destinationUri.

Acceptance Criteria

  • Job shape and bundle envelope above referenced from Sprint 123 Delivery Tracker; no other blocking dependencies.
  • Export artefacts can be consumed offline; notification optional.

Notes

  • Satisfies PREP-EXPORT-CONSOLE-23-001-MISSING-EXPORT-BUN.