stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity
Files
bc4318ef971247e18c9c05f8b7838880f6584dc3
git.stella-ops.org/docs2/data/events.md
master bc4318ef97 Add tests for SBOM generation determinism across multiple formats 
- Created `StellaOps.TestKit.Tests` project for unit tests related to determinism.
- Implemented `DeterminismManifestTests` to validate deterministic output for canonical bytes and strings, file read/write operations, and error handling for invalid schema versions.
- Added `SbomDeterminismTests` to ensure identical inputs produce consistent SBOMs across SPDX 3.0.1 and CycloneDX 1.6/1.7 formats, including parallel execution tests.
- Updated project references in `StellaOps.Integration.Determinism` to include the new determinism testing library.
2025-12-23 18:56:12 +02:00

1.4 KiB
Raw Blame History

Events and messaging

Platform services emit strongly typed events with JSON schemas. Event files use the pattern @.json and samples mirror the version.

Envelope types

  • Orchestrator events: versioned envelopes with idempotency keys and trace context.
  • Legacy Redis envelopes: transitional schemas used for older consumers.

Event catalog (examples)

  • scanner.event.report.ready@1 and scanner.event.scan.completed@1 (orchestrator envelopes).
  • scanner.report.ready@1 and scanner.scan.completed@1 (legacy Redis envelopes).
  • scheduler.rescan.delta@1, scheduler.graph.job.completed@1, attestor.logged@1.

Orchestrator envelope fields (v1)

  • eventId, kind, version, tenant
  • occurredAt, recordedAt
  • source, idempotencyKey, correlationId
  • traceId, spanId
  • scope, payload, attributes

Legacy envelope fields

  • eventId, kind, tenant, ts
  • scope, payload, attributes

Versioning rules

  • Additive changes stay in the same version.
  • Breaking changes require a new @ schema and matching sample.
  • Consumers should pin and log unknown versions.

Validation

  • Schemas and samples live under docs/events/ and docs/events/samples/.
  • Offline validation uses ajv-cli; keep schema checks deterministic.
  • Validate schemas with ajv compile and validate samples against matching schemas.
  • Add new samples for each new schema version.

Related references

  • docs/events/README.md
  • docs/runtime/SCANNER_RUNTIME_READINESS.md