Add a optional ttlSecondsAfterFinished field to scans to cleanup finished scans about securecodebox HOT 3 OPEN

Hi @danil-smirnov
No, scans right now have no automatic cleanup. Adding a ttlSecondsAfterFinished field would be cool. (simmilar to the field on k8s jobs: https://kubernetes.io/docs/concepts/workloads/controllers/ttlafterfinished/#cleanup-for-finished-jobs)

ScheduledScans however will automatically only keep around x number of the most recent scans. (configurable on the scheudledscan).

from securecodebox.

Thank you @J12934
If we switch to ScheduledScans and we create tens of them, is it possible to distribute their runs over time to avoid rate-limiting issues and save costs? I haven't found any cron-like syntax or a parameter to set the starting time.

from securecodebox.

Thank you @J12934 If we switch to ScheduledScans and we create tens of them, is it possible to distribute their runs over time to avoid rate-limiting issues and save costs? I haven't found any cron-like syntax or a parameter to set the starting time.

oh, whoops somehow that wen't missing in the docs. cron expression support was added in release 4.1.0
opened a pr to add the docs: https://github.com/secureCodeBox/secureCodeBox/pull/2296/files

from securecodebox.