S-B04 · docker-compose.local.yml can't complete the flow: unseeded zaaktype, undeployed DMN, no NRC abonnement #110
Closed
opened 2026-07-22 08:41:29 +00:00 by not
·
0 comments
No Branch/Tag Specified
main
ci/175-deploy-on-merge
feat/177-public-tls-edge
ci/168-helm-chart-ci-gate
docs/169-mkdocs-nav
feat/25-helm-kubernetes-caddy
fix/161-e2e-bounded-and-diagnosable
feat/162-werkbak-live-refresh
feat/132-medewerker-mfa
fix/156-tempo-ingester-healthcheck
feat/153-projection-sourced-from-objecten
feat/152-objecten-publishes-to-nrc
feat/149-acl-writes-registerrecord
feat/141-registerrecord-objecttype
perf/verify-stack-uwsgi-oz-nrc
fix/144-verify-stack-uwsgi
feat/140-objecten-up
feat/139-objecttypen-up
feat/131-default-fill-crud
chore/136-ci-job-summaries
fix/134-verify-stack-scheduling
feat/130-beheer-catalogi
feat/124-metrics-dashboards
ci/127-parallel-jobs
feat/123-distributed-traces
feat/111-self-service-resume
feat/113-acl-zaaktype-by-identificatie
fix/110-compose-local-flow
fix/115-e2e-single-worker
docs/111-backlog-s26
feat/106-close-zaak-on-timeout
feat/103-diploma-upload-documenten
feat/102-document-wait-timeout
feat/14-dmn-diploma-eligibility
feat/15-beoordeling-escalation
fix/portal-nginx-resolver
fix/local-eventsubscriber-acl
feat/12-withdrawal-portal
fix/91-local-compose-parity
feat/12-withdrawal-bff
feat/12-withdrawal-workflow
feat/12-withdrawal
feat/13-behandel-portal
feat/13-behandel-decide
feat/13-behandel-bff-auth-werkbak
feat/13-workflow-user-tasks
feat/13-behandel-decision-model
chore/release-2026.07.0
feat/78-reference-correlation
feat/75-approval-flow
feat/10-openbaar-portal
chore/73-ci-speedups
feat/68-e2e
feat/67-self-service-form
feat/66-api-client
feat/65-nx-workspace
feat/8-bff
feat/6-domain-service
feat/7-event-subscriber-projection
feat/56-nrc-notification-wiring
test/46-acl-openzaak-integration
feat/47-acl-mutation-baseline
ci/30-gitea-actions-ci
feat/5-acl-open-zaak
feat/4-flowable
feat/3-keycloak
feat/2-opennotificaties
feat/2-catalogus-seed
feat/10-openzaak-compose
feat/32-docs-scaffold
feat/31-contributor-workflow
feat/30-gitea-actions-ci
feat/29-bff-docker-compose
chore/remove-bootstrap-scripts
feat/28-bff-health
docs/split-s00
v2026.07.0
Milestone
No items
No Milestone
Iteration 2 — Flow Completeness
Projects
Clear projects
No projects
Assignees
eho (Edwin van den Houdt)
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: eho/register-referentie#110
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What happened:
On the
make localstack (infra/docker-compose.local.yml, the host-browser-friendly path), a registration submitted through the portals never completes the flow: it doesn't reach the behandel werkbak, and nothing appears in the openbaar (public) register. Three pieces of setup that theverify-*scripts perform against the CI stack are not done by the local stack's bring-up, so the compose file has drifted behind slices S-06, S-10a, and S-13:Unseeded zaaktype + unwired ACL.
acldefaultsAcl__Defaults__ZaaktypeUrlto the all-zeros placeholder UUID. No published BIG zaaktype is seeded and the ACL is never repointed at it, so zaak creation fails with OpenZaak400and the process sticks atOpenZaakAanmaken— nothing progresses at all. (Theverify-*scripts seed viainfra/openzaak/seed_catalogus.pywithOZ_PUBLISH=1and recreateaclpointed at the server-assigned URL. Note the localaclalso hardcodesAcl__OpenZaak__BaseUrl, with no override.)diploma-eligibilityDMN not deployed. The localflowable-initdeploys onlyregistratie.bpmn— notworkflows/diploma-eligibility.dmn. The CIinfra/docker-compose.ymlflowable-initdeploys both (the DMN via/flowable-rest/dmn-api/dmn-repository/deployments). CompletingWachtOpDocumentenruns the DMN routing task and Flowable returns404 "No decision found for key: diploma-eligibility", so the case never routes toBeoordelen(the task the werkbak lists).No NRC abonnement registered. The event-subscriber starts but never subscribes, so OpenZaak's
zakennotifications (create + status-set) go into NRC and are delivered nowhere →register_projectionstays empty → the openbaar register (GET /openbaar/register) shows nothing, including approved (INGESCHREVEN) rows. (Registered by the verify scripts viainfra/verify-notification-driver.py.)What you expected:
A fresh
make localshould be able to run the full demo end-to-end in the browser — submit → upload diploma → appear in the werkbak → goedkeuren → appear in the openbaar register as INGESCHREVEN — with no manual seeding.Steps to reproduce:
make down && make local.jan-burger / test123), submit a registration, upload a diploma.merel-behandelaar / test123) → the registration never appears (stuck atOpenZaakAanmaken; once that's fixed, stuck atWachtOpDocumentenbecause the DMN 404s).Environment:
main(atc8fdfbb), Fedora, rootless Podman viamake local(infra/docker-compose.local.yml). Reproduced live in-session; the CIverify-*stack is unaffected because those scripts do all three setup steps.Logs / evidence:
POST /zaken→400(placeholder zaaktype); domainOpenZaakAanmaken"leaving it for redelivery".POST /runtime/tasks/{id}(complete WachtOpDocumenten) →404 {"exception":"No decision found for key: diploma-eligibility ..."}.dmn-repository/decisionstotal 0; NRC has 0 abonnementen;register_projectionempty; event-subscriber log shows only startup.aclpointed at it; deploy the DMN viadmn-api; POST the abonnement to NRC pointed athttp://<es-ip>:8080/notificationswithBearer big-reference-notifications. After all three, a fresh submit flowed to the werkbak and the openbaar register correctly. These manual fixes are ephemeral (lost on the nextmake down && make local).Proposed fix: bring
docker-compose.local.ymlbring-up up to parity with theverify-*setup — deploy the DMN inflowable-init, seed + publish a BIG zaaktype and wire the ACL to it (allow overridingAcl__OpenZaak__BaseUrl), and register the NRC abonnement on startup — so a freshmake localcompletes the flow. Follows S-B01/S-B02/S-B03.Suspected area: area:infra (also touches workflow / event-subscriber / acl wiring, but the fix lives in the local compose + seed).