Revert "verify: allow '0' days for reverification"
This reverts commit 7a1a5d206d
.
We could already cause the behavior by simply setting ignore-verified
to false, aas that flag is basically an on/off switch for even
considering outdated-after or not.
So avoid the extra logic and just make the gui use the previously
existing way.
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
This commit is contained in:
parent
0f8fd71093
commit
327d14b3d1
@ -156,7 +156,7 @@ pub const IGNORE_VERIFIED_BACKUPS_SCHEMA: Schema = BooleanSchema::new(
|
|||||||
|
|
||||||
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 means always)")
|
||||||
.minimum(0)
|
.minimum(1)
|
||||||
.schema();
|
.schema();
|
||||||
|
|
||||||
#[api(
|
#[api(
|
||||||
|
@ -595,7 +595,7 @@ pub fn verify_filter(
|
|||||||
let now = proxmox_time::epoch_i64();
|
let now = proxmox_time::epoch_i64();
|
||||||
let days_since_last_verify = (now - last_verify.upid.starttime) / 86400;
|
let days_since_last_verify = (now - last_verify.upid.starttime) / 86400;
|
||||||
|
|
||||||
max_age == 0 || days_since_last_verify > max_age
|
days_since_last_verify > max_age
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
}
|
}
|
||||||
|
@ -507,7 +507,7 @@ Ext.define('PBS.DataStoreContent', {
|
|||||||
"backup-type": data["backup-type"],
|
"backup-type": data["backup-type"],
|
||||||
"backup-id": data["backup-id"],
|
"backup-id": data["backup-id"],
|
||||||
"backup-time": (data['backup-time'].getTime()/1000).toFixed(0),
|
"backup-time": (data['backup-time'].getTime()/1000).toFixed(0),
|
||||||
"outdated-after": 0, // always reverify single snapshots
|
"ignore-verified": false, // always reverify single snapshots
|
||||||
};
|
};
|
||||||
} else {
|
} else {
|
||||||
params = {
|
params = {
|
||||||
|
Loading…
Reference in New Issue
Block a user