eho/register-referentie
1
0
Fork 0
Code Issues 17 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

S-01 · OpenZaak + Open Notificaties + Postgres come up in compose #2

New Issue
Closed
opened 2026-06-03 09:52:55 +00:00 by eho · 1 comment
eho commented 2026-06-03 09:52:55 +00:00
Owner
Copy Link

Outcome: Local docker compose up brings up OpenZaak, Open Notificaties, their dependencies, and a seeded ZTC catalogus called BIG. A health check confirms all reachable.

Acceptance:

  • curl to OpenZaak /zaken/api/v1/zaken returns 403 PermissionDenied for a missing JWT — auth enforced. (Was "401"; OpenZaak's ZGW APIs use 403. Verified in S-01-a.)
  • A test client with a generated JWT can list zaaktypen in the BIG catalogus.
  • The seeded catalogus contains one lean BIG-registratie zaaktype with only the schema-mandatory fields plus bsn as an eigenschap.

Touches: infra/openzaak/, infra/opennotificaties/, infra/seed/, ADR for catalogus design.

Out of scope: any portal, BFF, Flowable, ACL code.

Definition of Done

  • A linked Gitea issue exists (this one).
  • Failing test written and committed first.
  • Implementation makes the test pass.
  • Refactor commit follows if structure improved.
  • Conventional Commit messages referencing this issue (refs #NN).
  • All Gitea Actions CI jobs green: lint, unit, integration, mutation (ratchet), e2e, container build + push, compose-up smoke test.
  • docker compose up from a fresh clone reaches green health checks within 3 minutes.
  • Docs touched if behaviour, contracts, or operations changed.
  • ADR added in docs/architecture/ if a non-obvious decision was made.
  • Demo note appended to docs/demo-script.md if the slice is user-visible.
  • This issue closed by the merging PR (closes #NN).
**Outcome:** Local `docker compose up` brings up OpenZaak, Open Notificaties, their dependencies, and a seeded ZTC catalogus called `BIG`. A health check confirms all reachable. **Acceptance:** - `curl` to OpenZaak `/zaken/api/v1/zaken` returns **403** `PermissionDenied` for a missing JWT — auth enforced. (Was "401"; OpenZaak's ZGW APIs use 403. Verified in S-01-a.) - A test client with a generated JWT can list zaaktypen in the `BIG` catalogus. - The seeded catalogus contains one lean `BIG-registratie` zaaktype with only the schema-mandatory fields plus `bsn` as an eigenschap. **Touches:** `infra/openzaak/`, `infra/opennotificaties/`, `infra/seed/`, ADR for catalogus design. **Out of scope:** any portal, BFF, Flowable, ACL code. ## Definition of Done - [ ] A linked Gitea issue exists (this one). - [ ] Failing test written and committed first. - [ ] Implementation makes the test pass. - [ ] Refactor commit follows if structure improved. - [ ] Conventional Commit messages referencing this issue (`refs #NN`). - [ ] All Gitea Actions CI jobs green: lint, unit, integration, mutation (ratchet), e2e, container build + push, compose-up smoke test. - [ ] `docker compose up` from a fresh clone reaches green health checks within 3 minutes. - [ ] Docs touched if behaviour, contracts, or operations changed. - [ ] ADR added in `docs/architecture/` if a non-obvious decision was made. - [ ] Demo note appended to `docs/demo-script.md` if the slice is user-visible. - [ ] This issue closed by the merging PR (`closes #NN`).
eho added this to the Iteration 1 — Walking Skeleton milestone 2026-06-03 09:52:55 +00:00
eho added the type:slicearea:infra labels 2026-06-03 09:52:55 +00:00
eho closed this issue 2026-06-03 13:59:03 +00:00
eho commented 2026-06-03 14:44:17 +00:00
Author
Owner
Copy Link

Tidy-up: acceptance corrected from 401 to 403. OpenZaak returns 403 PermissionDenied for a missing/invalid JWT (a ZGW fout), not 401 — verified in S-01-a (PR #40).

Tidy-up: acceptance corrected from 401 to **403**. OpenZaak returns `403 PermissionDenied` for a missing/invalid JWT (a ZGW fout), not 401 — verified in S-01-a (PR #40).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area:acl
area:bff
area:docs
area:domain
area:event-subscriber
area:infra
area:portal-behandel
area:portal-beheer
area:portal-openbaar
area:portal-self-service
area:projection
area:workflow
type:adr-proposal
type:bug
type:chore
type:slice
No Label area:infra type:slice
Milestone
No items
No Milestone Iteration 1 — Walking Skeleton
Projects
Clear projects
No project
Assignees
Clear assignees
eho
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: eho/register-referentie#2
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?