api types: verify job: allow outdated-afer == 0 for backward compat

We can have those in existing verify jobs configs, and that'd break
stuff. So, even while the "bad" commit got released only recently
with `2.1.6-1` (14 April 2022), we still need to cope with those that
used it, and using some serde parser magic to transform on read only
is hard here due to section config (json-value and verify currently
happen before we can do anything about it)

Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
Thomas Lamprecht 2022-05-18 15:39:57 +02:00
parent 327d14b3d1
commit 7f3b4a94e6
1 changed files with 2 additions and 2 deletions

View File

@ -155,8 +155,8 @@ pub const IGNORE_VERIFIED_BACKUPS_SCHEMA: Schema = BooleanSchema::new(
.schema(); .schema();
pub const VERIFICATION_OUTDATED_AFTER_SCHEMA: Schema = pub const VERIFICATION_OUTDATED_AFTER_SCHEMA: Schema =
IntegerSchema::new("Days after that a verification becomes outdated. (0 means always)") IntegerSchema::new("Days after that a verification becomes outdated. (0 is deprecated)'")
.minimum(1) .minimum(0)
.schema(); .schema();
#[api( #[api(