Open barmac opened 1 month ago
I just discovered that Camunda 8.6.0-alpha.3 will fall back to the latest decision when no decisions were deployed even though bindingType=deployment is set.
I am moving this to the backlog for now.
Note that this is "unusable" only when deploying from the Desktop modeler (where we want to support project awareness / multi-file deployments).
It is fully usable if you deploy or test, process application style, i.e. via spring-zeebe.
I propose we close and/or rephrase this issue to "the ability to deploy multiple files" with Zeebe.
I updated the title to phrase it as feature.
Describe the bug
With v5.26.0, a new property
bindingType
was introduced to some elements. It can be set todeployment
for Camunda 8.6 diagrams. However, Desktop Modeler supports a single file deployment only. So I cannot benefit from the feature as long as I deploy from Desktop Modeler.Steps to reproduce
bindingType
to deploymentExpected behavior
I can deploy multiple files. Either we could have a concept of process application like in Web Modeler, or simply expose a file picker like in the C7 deployment tool.
Environment
Additional context
Multi-file deployment was discussed in the weekly: https://github.com/bpmn-io/internal-docs/issues/1015#issuecomment-2245121338 Brought up again via Slack: https://camunda.slack.com/archives/GP70M0J6M/p1722590739493789?thread_ts=1722511667.499869&cid=GP70M0J6M
Related to https://github.com/camunda/product-hub/issues/2458