Niek Otten
7ef63c7ae9
Add the projection persistence and the two services around it:
- Projection.ReadModel: a shared EF Core (Npgsql) read model owning the projection
schema — register_projection + the subscriber's processed_notifications log — plus
EfProjectionStore / EfNotificationLog (atomic record-or-skip on the PK for idempotency)
and the initial migration. One rebuildable store, written by the subscriber and read
by projection-api (ADR-0008).
- EventSubscriber.Api: POST /notifications NRC callback (enforces the abonnement bearer,
401 without it per ADR-0007), POST /admin/rebuild, /health. Migrates on start.
- ProjectionApi.Api: GET /register, GET /register/{id}, /health — the read side.
dotnet-ef pinned as a local tool for migrations; NuGetAuditMode=direct so EF's
design-time-only tooling transitive doesn't flag the shipped build.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
20 lines
321 B
JSON
20 lines
321 B
JSON
{
|
|
"version": 1,
|
|
"isRoot": true,
|
|
"tools": {
|
|
"dotnet-stryker": {
|
|
"version": "4.15.0",
|
|
"commands": [
|
|
"dotnet-stryker"
|
|
],
|
|
"rollForward": false
|
|
},
|
|
"dotnet-ef": {
|
|
"version": "10.0.0",
|
|
"commands": [
|
|
"dotnet-ef"
|
|
],
|
|
"rollForward": false
|
|
}
|
|
}
|
|
} |