Custom Script Deployment - Question regarding updating Resource

My camunda

  • Runs inside a Docker

My custom-scripts

  • Should be accessible from the outside of the container
  • Will be updated on a regularly basis

As of now my approach works as followed:

  • Scripts will be mounted via Docker Volume
  • /camunda/lib/{myFolder}/{myScript}.js

I therefore assume, that this /lib is somewhere on the classpath://, which is an allowed source for external Ressources in the script Task, fine by me. :slight_smile:

Next step would be to make sure, that the latest version of the script is executed with next Workflowinstance created. But - I found that the script is not read dynamically from the folder but bound to the process definition in a static manner.

There are two ways to force usage of the newest script:

  • Create a new Deployment of the Workflow Definition
  • Restart the camunda Container

As restarting has the same effect as redeployment has, the binding seems not to be so static - but more or less the script is cached somewhere.

This leads me to my Question:

As of now i have no nomalized behavior in terms of script versioning. It would be nice to always be sure that one way or another the script is updated or is not updated.

Is there a way to force a “cache renewal” on changing a script file e.g.?

Looking forward to your reply’s, thanks in advance!

sincerly
Andre