public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Lukas Wagner <l.wagner@proxmox.com>
To: Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>,
	Philipp Hufnagl <p.hufnagl@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup v2 3/3] docs: document new include/exclude paramenter
Date: Tue, 28 Nov 2023 10:30:38 +0100	[thread overview]
Message-ID: <89a690b1-1497-4562-a615-6d6ca08693fb@proxmox.com> (raw)
In-Reply-To: <20231109144329.1830522-4-p.hufnagl@proxmox.com>



On 11/9/23 15:43, Philipp Hufnagl wrote:
> Adding the newly introduced optional include/exclude parameter to the
> PBS documentation.
> 
> Signed-off-by: Philipp Hufnagl <p.hufnagl@proxmox.com>
> ---
>   docs/managing-remotes.rst | 8 ++++++++
>   1 file changed, 8 insertions(+)
> 
> diff --git a/docs/managing-remotes.rst b/docs/managing-remotes.rst
> index 1c52e120..2f08c3b1 100644
> --- a/docs/managing-remotes.rst
> +++ b/docs/managing-remotes.rst
> @@ -116,6 +116,14 @@ of the specified criteria are synced. The available criteria are:
>   The same filter is applied to local groups, for handling of the
>   ``remove-vanished`` option.
>   
> +A ``group-filter`` can be inverted by adding ``exclude:`` to its beginning.
> +
> +* Regular expression example, excluding the match:
> +    .. code-block:: console
> +
> +     # proxmox-backup-manager sync-job update ID --group-filter exclude:regex:'^vm/1\d{2,3}$'
> +
> +If include as well as exclude filters are used, all include filters will be run before the exclude filters.

Maybe it would make sense here to enumerate the different cases and 
their exact behaviors, e.g. in a table?

  - no filters: all backup groups
  - include: only those matching the include filters
  - exclude: all but those matching the exclude filters
  - both: those matching the include filters, but without those matching 
the exclude filters

Also, I'm not sure if 'will be run before' is easy to understand for 
users. I think something alike how I described the 'both' case should be 
easier to understand


-- 
- Lukas




      reply	other threads:[~2023-11-28  9:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 14:43 [pbs-devel] [PATCH proxmox-backup v2 0/3] fix #4315: datastore: Exclude entries from sync Philipp Hufnagl
2023-11-09 14:43 ` [pbs-devel] [PATCH proxmox-backup v2 1/3] fix #4315: jobs: modify GroupFilter so include/exclude is tracked Philipp Hufnagl
2023-11-28  9:11   ` Lukas Wagner
2023-11-09 14:43 ` [pbs-devel] [PATCH proxmox-backup v2 2/3] ui: Show if Filter includes or excludes Philipp Hufnagl
2023-11-28  9:57   ` Lukas Wagner
2023-11-09 14:43 ` [pbs-devel] [PATCH proxmox-backup v2 3/3] docs: document new include/exclude paramenter Philipp Hufnagl
2023-11-28  9:30   ` Lukas Wagner [this message]

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=89a690b1-1497-4562-a615-6d6ca08693fb@proxmox.com \
    --to=l.wagner@proxmox.com \
    --cc=p.hufnagl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal