3ae21d87c1
to avoid drifting definitions and reduce duplication. with the next major release, the 'upid' field could then be renamed and aliased to be in line with the other jobs, which all use 'last-run-upid'. doing it now would break existing callers of the GC status endpoint (or consumers of the on-disk status file). the main difference is that the GC status fields are now not optional (except for the UPID) in the job status, since flattening an optional value is not possible. this only affects datastores that were never GCed at all, and only direct API consumers, since the UI handles those fields correctly. Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com> |
||
|---|---|---|
| .. | ||
| src | ||
| tests | ||
| Cargo.toml | ||