Restart Postprocessing Properly

[kobergj]

Allows differentiating between "restart" and "resume" postprocessing

[mmattel]

@kobergj this is docs relevant, needs a change in: https://github.com/owncloud/ocis/tree/master/services/postprocessing#cli-commands
I also referenced the admin docs, beause we have a listing of changed CLI here too.

[wkloucek]

Allows differentiating between "restart" and "resume" postprocessing

Would the oCIS chart need have another CronJob next to ocis storage-users uploads sessions --restart --processing=true (https://github.com/owncloud/ocis-charts/blob/ce1b1c183b37bfda17f3114fce90b1f0f885da04/charts/ocis/templates/storageusers/jobs.yaml#L262C22-L262C95), that also calls the resume command?

I'm a little bit confused what actually needs to be run to cater all the different "postprocessing stuck" situations that can happen.

[kobergj]

restart will restart post processing of an upload from the very beginning. This allows retrying otherwise stuck uploads.

resume will resume postprocessing from the last finished step. This will cost less resources but doesn't work in all cases.

You could always call restart or call resume in specific situations to save resources.

[kobergj]

I'll prepare a hotfix once this is merged. This should enable us to get the files back.

[kobergj]

@wkloucek should we merge this so I can proceed with the backport? Or you have additional suggestions?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[ScharfViktor]

tested during the Patch release 5.0.9
ocis/bin/ocis postprocessing resume - works
ocis/bin/ocis postprocessing restart - works

I understand diffirence between commands but couldn't find the way how to test it localy