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

fix(infra): deploy BPMN + DMN as one .bar so the inline decision resolves (S-13, refs #14)
Some checks failed
CI / lint (pull_request) Successful in 1m17s
Details
CI / build (pull_request) Successful in 55s
Details
CI / unit (pull_request) Successful in 1m8s
Details
CI / frontend (pull_request) Successful in 2m31s
Details
CI / mutation (pull_request) Successful in 5m11s
Details
CI / verify-stack (pull_request) Failing after 7m44s
Details

Browse Source 
The DMN service task resolves its decision scoped to the process's own deployment,
so a standalone .dmn deployment was invisible (FlowableObjectNotFoundException: No
decision found for key: diploma-eligibility). Bundle registratie.bpmn +
diploma-eligibility.dmn into a single registratie.bar and deploy it as one
deployment, giving the decision the process's parent deployment id. flowable-rest
does not expose the dmn-api app, so co-deployment is the way in.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Niek Otten
2026-07-18 11:38:44 +02:00
parent 60ea61f0ed
commit d5100d9d41
4 changed files with 35 additions and 28 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
infra/docker-compose.yml
View File

@@ -259,7 +259,8 @@ services:
flowable-init:
image: docker.io/curlimages/curl:latest
restart: "no"
# registratie.bpmn + diploma-eligibility.dmn are streamed into this external volume by infra/seed-config.sh.
# registratie.bar (registratie.bpmn + diploma-eligibility.dmn) is streamed into this external
# volume by infra/seed-config.sh.
volumes:
- fl-bpmn:/work:ro
command:
@@ -268,19 +269,13 @@ services:
- |
base=http://flowable-rest:8080/flowable-rest/service/repository/deployments
until curl -sf -u rest-admin:test "$$base" >/dev/null 2>&1; do echo "waiting for flowable-rest..."; sleep 3; done
# Deploy the diploma-eligibility DMN via the process repository: the flowable-rest image embeds
# the DMN engine but does not expose the dmn-api app, so the process deployment cross-deploys the
# .dmn resource to the DMN engine, where the registratie DMN service task resolves it by key
# (S-13, ADR-0016).
if curl -s -u rest-admin:test "$$base?name=diploma-eligibility" | grep -q '"name":"diploma-eligibility"'; then
echo "diploma-eligibility already deployed; skip"
else
curl -sf -u rest-admin:test -F 'file=@/work/diploma-eligibility.dmn;filename=diploma-eligibility.dmn' "$$base" >/dev/null && echo "deployed diploma-eligibility"
fi
# Deploy the BPMN + its DMN as ONE .bar so the inline DMN service task resolves the decision by
# the process's own (shared) parent deployment id — flowable-rest does not expose the dmn-api app,
# and a standalone .dmn deployment is not visible to the process (S-13, ADR-0016).
if curl -s -u rest-admin:test "$$base?name=registratie" | grep -q '"name":"registratie"'; then
echo "registratie already deployed; skip"
else
curl -sf -u rest-admin:test -F 'file=@/work/registratie.bpmn;filename=registratie.bpmn' "$$base" >/dev/null && echo "deployed registratie"
curl -sf -u rest-admin:test -F 'file=@/work/registratie.bar;filename=registratie.bar' "$$base" >/dev/null && echo "deployed registratie (bpmn + dmn)"
fi
depends_on:
flowable-rest: