S-01-c · Wire OpenZaak → Open Notificaties (enable & publish notifications) #56

New Issue

not · 2026-06-29T11:54:55Z

not commented

2026-06-29 11:54:55 +00:00

Split/deferred from #2 (S-01). S-01 brought OpenZaak + Open Notificaties (NRC) + Postgres up in compose, but the notification wiring between them was intentionally deferred — OpenZaak runs with NOTIFICATIONS_DISABLED: "true" and NRC's setup_configuration is empty ({}). The data.yaml comment marks this as "S-01-c".

Outcome: A zaak created in OpenZaak publishes a zaken-kanaal notification that Open Notificaties (NRC) accepts and can fan out to subscribers — the upstream half of the event path the Event Subscriber (#7) consumes.

Acceptance:

OpenZaak NOTIFICATIONS_DISABLED off; OpenZaak configured with the Notificaties API service + credentials to publish to NRC.
NRC setup_configuration provisions the JWT credential(s), the zaken kanaal (and any others OpenZaak requires to boot), and the authorizations so OpenZaak may publish.
Verification: creating a zaak (the published BIG zaaktype from the seed) results in a notification delivered to a test abonnement (e.g. a throwaway webhook sink), asserted in CI like the other *-smoke checks.
Idempotent + repeatable from a fresh make bring-up; works on the hosted runner (no host-port access — see gitea-actions-gotchas.md §5).

Touches: infra/openzaak/, infra/opennotificaties/setup_configuration/, infra/docker-compose.yml, Makefile (a smoke/verify target), docs. Likely an ADR for the notification-wiring approach.

Out of scope: the Event Subscriber service and the projection (#7); decision/besluit notifications.

Blocks #7. Refs #2.

Split/deferred from #2 (S-01). S-01 brought OpenZaak + Open Notificaties (NRC) + Postgres up in compose, but the **notification wiring** between them was intentionally deferred — OpenZaak runs with `NOTIFICATIONS_DISABLED: "true"` and NRC's `setup_configuration` is empty (`{}`). The data.yaml comment marks this as "S-01-c". **Outcome:** A zaak created in OpenZaak publishes a `zaken`-kanaal notification that Open Notificaties (NRC) accepts and can fan out to subscribers — the upstream half of the event path the Event Subscriber (#7) consumes. **Acceptance:** - OpenZaak `NOTIFICATIONS_DISABLED` off; OpenZaak configured with the Notificaties API service + credentials to publish to NRC. - NRC `setup_configuration` provisions the JWT credential(s), the `zaken` kanaal (and any others OpenZaak requires to boot), and the authorizations so OpenZaak may publish. - Verification: creating a zaak (the published BIG zaaktype from the seed) results in a notification delivered to a test abonnement (e.g. a throwaway webhook sink), asserted in CI like the other `*-smoke` checks. - Idempotent + repeatable from a fresh `make` bring-up; works on the hosted runner (no host-port access — see gitea-actions-gotchas.md §5). **Touches:** `infra/openzaak/`, `infra/opennotificaties/setup_configuration/`, `infra/docker-compose.yml`, Makefile (a smoke/verify target), docs. Likely an ADR for the notification-wiring approach. **Out of scope:** the Event Subscriber service and the projection (#7); decision/besluit notifications. Blocks #7. Refs #2.

not added this to the Iteration 1 — Walking Skeleton milestone 2026-06-29 11:54:55 +00:00

not added the area:infra type:slice labels 2026-06-29 11:54:55 +00:00

not referenced this issue from a commit

2026-06-29 12:29:34 +00:00

feat(infra): wire OpenZaak → Open Notificaties notifications (refs #56)

not referenced this issue from a commit

2026-06-29 12:29:34 +00:00

test(infra): verify-notifications smoke + CI job for the OZ→NRC path (refs #56)

not referenced this issue from a commit

2026-06-29 12:29:34 +00:00

arch(infra): ADR-0007 + runbooks for the OZ→NRC notification wiring (refs #56)

not referenced a pull request that will close this issue