occ background-job:delete

[ArtificialOwl]

allow an admin to remove a background job entry from the database

[nickvergessen]

This is potentially very dangerous and at the same time some apps might regenerate their jobs.
So far I never had the case where an admin would have needed to delete a job? Can you give an example?

[nickvergessen]

Suggested change

	class DeleteCommand extends Base {
	class DeleteJob extends Base {

?

[ArtificialOwl]

This is potentially very dangerous and at the same time some apps might regenerate their jobs. So far I never had the case where an admin would have needed to delete a job? Can you give an example?

The only one I have in mind right now is this issue with a background job that could not resolve itself:
#42489

It is a unique job that remove itself when its purpose is over.
While this job should be fixed by #42667 it also made us realize there is no easy way to cancel it

[come-nc]

Please just name the file Delete.php and the class Delete if the command is :delete.

ListCommmand is called ListCommand because list is a reserved keyword, delete is not.

[joshtrichards]

Could "hide" being NC_debug but the built-in confirmation might also be enough warning.

[ArtificialOwl]

/backport to stable28

[backportbot-nextcloud]

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28

# Create the new backport branch
git checkout -b fix/foo-stable28

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable28

Error: Unknown error

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport