Details
-
Bug Report
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
Description
Steps to reproduce:
- create a process application with a dmn table
- deploy the process application for example to jboss => a new deployment is available with deployment source "process application" and a decision definition exists with version 1
- go to cockpit
- do a live adjustment of the dmn table and deploy the changed dmn table => a second deployment is available with deployment source "cockpit" and a decision definition exists with version 2
- download the latest dmn table
- update the process application with the latest dmn table
- re-deploy the process application => a third deployment is available with deployment source "process application" and a decision definition exists with version 3
Problem:
The decision definition with version 3 is a duplicate of the decision definition with version 2.
Expected Behavior:
When the duplicate checking is enabled and the resources does not differ (independent from deployment source), there is no new version of the definition resource.
Hint:
The duplicate check could be extended in the following way:
For each resource to deploy:
- Get the last resource with the same name (independent from the deployment source): If it is a duplicate, then do not deploy the resource and return
- Get the last resource with the same name and deployment source-aware: If it is duplicate, then do not deploy the resource and return
- Otherwise deploy the resource
mgm-controller-panel
This is the controller panel for Smart Panels app
Attachments
Issue Links
- is related to
-
CAM-4710 I can set a source of a deployment
- Closed