When service restarts are implemented for scap3, there should be an arg to specify a delay time between each batch being run, in case the service needs time to 'warm up' a cache or what have you.
Description
Description
Event Timeline
Comment Actions
This might be tricky since scap3 doesn't do batches per se but concurrency levels. A post-stage check could be leveraged to induce a delay, however.
checks: warm_cache: type: command command: sleep 60 stage: promote
It's a bit hacky but, if the check were to actually instrument something over time, I could see it being congruent with the check system.