show and delete deployments.
engagement, I thought about how to clean up my database from all the
failing process diagrams that I don’t need any more. I asked Bernd how to
get rid of the old stuff. He deleted the H2 files from his computer.
That’s a very fresh start. And he is now very fast in finding and
installing the enterprise license key again. This could be done better in my
saw a test system with version 168 of the process definition to test.
Someone should clean up here. But how?
about deleting the deployment with cascade=true? Who calls the Java-API and when? An engine plugin seems too complicated for this and somehow you have to get the IDs of the deployments to delete.
rest-clients, it should be easy to call repositoryService.
But it wasn’t implemented as a REST service. There wasn’t even a REST deployment service. The team built it for 7.2. But they missed the
delete method. Was it a security issue? If someone is able to call
deleteDeployment with cascade=true, he will delete all current process
instances and even the history, too.
Robert told me, that there weren’t any security concerns, it was just not so important for the team. So I looked at the rest-implementation how to
delete process instances and made a contribution to delete deployments.
Cockpit Plugin Archetype
the advanced training Falko introduced the plugin archetype and with this
very easy approach I quickly wrote a cockpit plugin that deletes
deployments on the server side, without a graphical user interface. I
installed it on my favorite Jboss 7.1.5 Enterprise version to get rid of
the old deployments. I deleted them with the ID from the
database and called the cockpit plugin rest service with a rest client.
divided the files into controllers and resources.
Now I created a deployment-plugin from the archetype, chose
7.2.0-alpha5 as camunda version and started to write some code.
decide, which deployments can be deleted without harming the system,
you need the number of running process instances for the process
definitions of the deployment together with deployment times. Ok, that’s a
three-stage folding of three different resources. Deployment – Process
Definitions – Process Instances. A deep dive into angular coding, but it
went quite well. I extracted some services, and used a date-picker for selection criteria. Coffeehouses in Vienna are a good place to do this.
Cafe Ritter with free Wi-Fi access or Cafe Bräunerhof where you have to
be better prepared as they don’t offer Wi-Fi access. Wiener Melange helps
it in the plugin store. The one missing piece is the refresh after
coming back from the confirmation popup. To implement it in a brute force way I
Camunda Developer Community
Join Camunda’s global community of developers sharing code, advice, and meaningful experiences