[PATCH proxmox-backup 1/2] proxy: scheduler: drop early return for keep-all prune jobs

[Christian Ebner <c.ebner@proxmox.com>]

It is currently possible to configure a prune job without any
keep options set, which will result in keeping all snapshots.

The proxy does an early check for this, not even recalculating the
schedule in that case and never creating any task. This caused some
confusion as reported in the enterprise support, as the prune job
reports pending state and is never executed if not triggered
manually.

Since it can make sense to create a scheduled job with keep-all for
testing reasons, drop the early check so the configured schedule is
honored, the task log containing the relevant info for the user on
why no snapshots are being pruned.

Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
 src/bin/proxmox-backup-proxy.rs | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/src/bin/proxmox-backup-proxy.rs b/src/bin/proxmox-backup-proxy.rs
index b372f779e..eb5443992 100644
--- a/src/bin/proxmox-backup-proxy.rs
+++ b/src/bin/proxmox-backup-proxy.rs
@@ -642,10 +642,6 @@ async fn schedule_datastore_prune_jobs() {
             continue;
         }
 
-        if !job_config.options.keeps_something() {
-            continue; // no 'keep' values set, keep all
-        }
-
         let worker_type = "prunejob";
         let auth_id = Authid::root_auth_id().clone();
         if check_schedule(worker_type, &job_config.schedule, &job_id) {
-- 
2.47.3