public inbox for pbs-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Christian Ebner <c.ebner@proxmox.com>,
	Proxmox Backup Server development discussion
	<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] api types: add missing conf to blob archive name mapping
Date: Tue, 26 Nov 2024 13:52:53 +0100	[thread overview]
Message-ID: <8bf0f5de-65ec-45f0-ab67-4ed76a89977c@proxmox.com> (raw)
In-Reply-To: <2cae33de-6348-46b1-8986-98d2e45e8a1c@proxmox.com>

Am 26.11.24 um 13:48 schrieb Christian Ebner:
> On 11/26/24 13:35, Thomas Lamprecht wrote:
>> Am 26.11.24 um 13:24 schrieb Christian Ebner:
>>> Commit addfae26 ("api types: introduce `BackupArchiveName` type")
>>> introduced a dedicated archive name api type to add rust type
>>> checking and bundle helpers to the api type. Since this, the backup
>>> archive name to server archive name mapping is handled by its parser.
>>
>> This is mostly relevant for the client or? I.e., this has no impact on
>> community implementations/experiments adding completely different archive
>> types?
> 
> No, this is not limited to the client. This is mostly used server side 
> to map the archive name extension to the server archive name extension 
> (.blob, .fidx, .didx).
> 
> The current mappings were already enforced/assumed by the server to some 
> extend, and other archive types must use the full server archive name 
> extension anyways, for the server to recognize it.
> 
> For community implementations: they will be affected by this as well, 
> but they would already have need to pass the full server archive name 
> extensions anyways. So this should not break anything for them.
> 

Ok, thank you for your explanation!


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


      reply	other threads:[~2024-11-26 12:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 12:24 Christian Ebner
2024-11-26 12:32 ` [pbs-devel] applied: " Fabian Grünbichler
2024-11-26 12:35 ` [pbs-devel] " Thomas Lamprecht
2024-11-26 12:41   ` Fabian Grünbichler
2024-11-26 12:48   ` Christian Ebner
2024-11-26 12:52     ` Thomas Lamprecht [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=8bf0f5de-65ec-45f0-ab67-4ed76a89977c@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=c.ebner@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