all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox v2 1/1] pbs-api-types: add 'unmount-on-done' field to sync job config
Date: Tue, 11 Nov 2025 13:08:57 +0100	[thread overview]
Message-ID: <1762862146.t8vqgbe2um.astroid@yuna.none> (raw)
In-Reply-To: <20251029160103.241780-2-h.laimer@proxmox.com>

On October 29, 2025 5:00 pm, Hannes Laimer wrote:
> Tested-by: Robert Obkircher <r.obkircher@proxmox.com>
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
> ---
>  pbs-api-types/src/jobs.rs | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/pbs-api-types/src/jobs.rs b/pbs-api-types/src/jobs.rs
> index 3eb61cde..3284a4c8 100644
> --- a/pbs-api-types/src/jobs.rs
> +++ b/pbs-api-types/src/jobs.rs
> @@ -538,6 +538,8 @@ pub const SYNC_VERIFIED_ONLY_SCHEMA: Schema =
>      BooleanSchema::new("Only synchronize verified backup snapshots, exclude others.").schema();
>  pub const RUN_SYNC_ON_MOUNT_SCHEMA: Schema =
>      BooleanSchema::new("Run this job when a relevant datastore is mounted.").schema();
> +pub const UNMOUNT_ON_SYNC_DONE_SCHEMA: Schema =
> +    BooleanSchema::new("Unmount involved removable datastore after sync job finishes.").schema();
>  
>  #[api(
>      properties: {
> @@ -609,6 +611,10 @@ pub const RUN_SYNC_ON_MOUNT_SCHEMA: Schema =
>              schema: RUN_SYNC_ON_MOUNT_SCHEMA,
>              optional: true,
>          },
> +        "unmount-on-done": {
> +            schema: UNMOUNT_ON_SYNC_DONE_SCHEMA,
> +            optional: true,
> +        },
>          "sync-direction": {
>              type: SyncDirection,
>              optional: true,
> @@ -655,6 +661,8 @@ pub struct SyncJobConfig {
>      #[serde(skip_serializing_if = "Option::is_none")]
>      pub run_on_mount: Option<bool>,
>      #[serde(skip_serializing_if = "Option::is_none")]
> +    pub unmount_on_done: Option<bool>,

could we combine these two into a property string/option, to make it
more explicit that the "unmount when done" part is only valid/relevant
for the "synced-cause-of-mount" execution?

> +    #[serde(skip_serializing_if = "Option::is_none")]
>      pub sync_direction: Option<SyncDirection>,
>  }
>  
> -- 
> 2.47.3
> 
> 
> 
> _______________________________________________
> pbs-devel mailing list
> pbs-devel@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
> 
> 
> 


_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel


  reply	other threads:[~2025-11-11 12:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 16:00 [pbs-devel] [PATCH proxmox{, -backup} v2 0/5] unmount datastores after sync job Hannes Laimer
2025-10-29 16:00 ` [pbs-devel] [PATCH proxmox v2 1/1] pbs-api-types: add 'unmount-on-done' field to sync job config Hannes Laimer
2025-11-11 12:08   ` Fabian Grünbichler [this message]
2025-11-11 12:26     ` Hannes Laimer
2025-11-11 13:43       ` Fabian Grünbichler
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 1/4] api: syncjob: correctly update/delete 'unmount-on-done' field Hannes Laimer
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 2/4] api: datastore: unmount datastore after sync if configured Hannes Laimer
2025-11-11 12:07   ` Fabian Grünbichler
2025-11-11 12:24     ` Hannes Laimer
2025-11-11 12:56       ` Fabian Grünbichler
2025-11-11 13:03         ` Hannes Laimer
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 3/4] ui: add 'unmount-on-done' field to SyncJobEdit window Hannes Laimer
2025-10-29 16:01 ` [pbs-devel] [PATCH proxmox-backup v2 4/4] docs: add section about `unmount-on-done` Hannes Laimer
2025-11-12 12:06 ` [pbs-devel] superseded: [PATCH proxmox{, -backup} v2 0/5] unmount datastores after sync job Hannes Laimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1762862146.t8vqgbe2um.astroid@yuna.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=pbs-devel@lists.proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal