Passing parameters to ScheduledScan about securecodebox HOT 1 OPEN

Cool idea but not sure if we can or if we should support it.

couples of thoughts:

1. Using initContainers to generate the parameters would be hard to impossible. The scans parameters are passed to the scan as args to the scanner container. I'm pretty sure this field is immutable on a pod or at least changing it after the pod is scheduled to a node doesn't have an effect.
   I think what is possible is to change the value in a configmap / secret the pod is mounting e.g. to inject a environments variable. The scan container could then use the value in the environment variable to generate the parameters but this wouldn't work when the scan container doesn't have a shell init. e.g. because it's build using a distroless image
2. Determining the parameters at runtime would make it really hard to debug why a scan is failing. especially if the value would also only be around at runtime.

for now if you need to change the parameters of a scheduledScan I'd suggest to do it simmilarly to the auto-discovery which changes the parameters of the scheduledscan and then triggers a premature execution of it by resetting the last executed at timestamp of the scheduledScan, which triggers a new execution right away. https://github.com/secureCodeBox/secureCodeBox/blob/main/operator/utils/retrigger_scheduled_scan.go#L17

It's not the nicest thing but works really well.

if somebody is willing to sketch out a design of a "dynamic parameter generator" for schedueld scans I'd be very interessted in looking at this :D (espeically if the the people would also be willing to implement and maintain it :) )

from securecodebox.