-
Type:
Bug Report
-
Resolution: Cannot Reproduce
-
Priority:
L3 - Default
-
None
-
Affects Version/s: 7.7.0, 7.8.0-alpha4, spring-boot 2.3.0-alpha1
-
Component/s: None
-
None
Hi,
not sure if this is an issue at all or misunderstanding on my side.
And not sure if its camunda-bpm-spring-boot-starter related, or core.
When deployment aware feature is truned on and you deploy a process that already exists, all other processes that were initially deployed with that process, get set to "executable" on that instance/node, too.
I would have expected, that only processes that are currently deployed in an instance would be executed.
To illustrate what I mean, I've created a minimal project setup with two instances here: https://github.com/icyerasor/camunda-deployment-aware
Tested with spring-boot 2.2.0 and 2.3.0-SNAPSHOT ( f9414fa)