Feature | Prunable

[simple-hacker]

Added the Prunable trait to the Workflow model, allowing a scheduled command to keep these tables size down. I have also added a new config value for how for how many days we should keep the Workflow models for when pruning.

I am happy to change the config property name, and the default values to something more suitable if required.

In our application, we'll be running lots of Workflows, and because the the callbacks are serialised, we found we had to change the database column from a text to a longtext to allow bigger workflows. Keeping these Venture workflow job without pruning will result in our database getting bigger and bigger. With Prunable we can help keep our database size down, as for our purposes, once it's been a week we no longer care about the workflow as these would've been processed by then.

[simple-hacker]

I just had a thought, should the prunable query be ran on both the finished_at and cancelled_at columns instead of the created_at? If people have Workflows that have jobs that are delayed longer than the config is set then it would remove the workflow.