[PATCH proxmox v3 02/10] pbs-api-types: prune job: make schedule optional

[Jonas Theisen <j.theisen@proxmox.com>]

To align the prune job API to the other job types and
to make use of the disable parameter the schedule should be optional.
If this is not the case a new prune job cannot be created to be
manually run i.e. disabled without a schedule.

This also means the schedule should be an Option<String> instead
of a plain String. This is based on the existing other jobs.

Signed-off-by: Jonas Theisen <j.theisen@proxmox.com>
---
 pbs-api-types/src/jobs.rs | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/pbs-api-types/src/jobs.rs b/pbs-api-types/src/jobs.rs
index 73d7c13f..9587971a 100644
--- a/pbs-api-types/src/jobs.rs
+++ b/pbs-api-types/src/jobs.rs
@@ -924,6 +924,7 @@ impl PruneJobOptions {
             schema: DATASTORE_SCHEMA,
         },
         schedule: {
+            optional: true,
             schema: PRUNE_SCHEDULE_SCHEMA,
         },
         comment: {
@@ -950,7 +951,8 @@ pub struct PruneJobConfig {
     #[updater(serde(skip_serializing_if = "Option::is_none"))]
     pub disable: bool,
 
-    pub schedule: String,
+    #[serde(skip_serializing_if = "Option::is_none")]
+    pub schedule: Option<String>,
 
     #[serde(skip_serializing_if = "Option::is_none")]
     pub comment: Option<String>,
-- 
2.47.3