[pve-devel] applied: [PATCH manager v9 02/13] api: jobs: vzdump: pass job 'job-id' parameter

[Thomas Lamprecht]

Am 08/07/2024 um 11:38 schrieb Lukas Wagner:
> This allows us to access the backup job id in the send_notification
> function, where we can set it as metadata for the notification.
> The 'job-id' parameter can only be used by 'root at pam' to prevent
> abuse. This has the side effect that manually triggered backup jobs
> cannot have the 'job-id' parameter at the moment. To mitigate that,
> manually triggered backup jobs could be changed so that they
> are not performed by a direct API call by the UI, but by requesting
> pvescheduler to execute the job in the near future (similar to how
> manually triggered replication jobs work).
> 
> Signed-off-by: Lukas Wagner <l.wagner at proxmox.com>
> Reviewed-by: Max Carrara <m.carrara at proxmox.com>
> ---
>  PVE/API2/Backup.pm |  2 +-
>  PVE/API2/VZDump.pm | 13 +++++++++++--
>  PVE/Jobs/VZDump.pm |  4 +++-
>  PVE/VZDump.pm      |  6 +++---
>  4 files changed, 18 insertions(+), 7 deletions(-)
> 
>

applied with the d/control bump for guest-common squashed in, thanks!