From: "Lukas Wagner" <l.wagner@proxmox.com>
To: "Fiona Ebner" <f.ebner@proxmox.com>,
"Lukas Wagner" <l.wagner@proxmox.com>,
<pbs-devel@lists.proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH pve-storage 7/7] api: add /nodes/<node>/storage/<storage>/identity route
Date: Fri, 17 Apr 2026 11:11:05 +0200 [thread overview]
Message-ID: <DHVBALQJTVEW.3J1RKLBCCGHJO@proxmox.com> (raw)
In-Reply-To: <262d3355-b8ec-470c-8fed-32a7b151fee4@proxmox.com>
On Fri Apr 17, 2026 at 10:54 AM CEST, Fiona Ebner wrote:
> Am 15.04.26 um 1:57 PM schrieb Lukas Wagner:
>> @@ -308,6 +308,7 @@ __PACKAGE__->register_method({
>> { subdir => 'download-url' },
>> { subdir => 'file-restore' },
>> { subdir => 'import-metadata' },
>> + { subdir => 'identity' },
>
> Just bike-shedding, but I'm wondering if 'identifier' would be slightly
> more natural?
I can change it if you prefer, but I think I prefer 'identity', if I'm
honest.
prev parent reply other threads:[~2026-04-17 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 11:58 [PATCH common/proxmox{,-backup}/storage 0/7] establish unique instance-id for PBS nodes Lukas Wagner
2026-04-15 11:58 ` [PATCH proxmox 1/7] pbs-api-types: add ServerIdentity response type Lukas Wagner
2026-04-15 11:58 ` [PATCH proxmox 2/7] systemd: add support for machine-id generation Lukas Wagner
2026-04-15 11:58 ` [PATCH proxmox-backup 3/7] api: add /nodes/localhost/server-identity Lukas Wagner
2026-04-15 11:58 ` [PATCH proxmox-backup 4/7] client: add 'server-identity' sub-command Lukas Wagner
2026-04-15 11:58 ` [PATCH proxmox-backup 5/7] manager: add 'server-identity' subcommand Lukas Wagner
2026-04-15 11:58 ` [PATCH common 6/7] pbs-client: add support for the 'server-identity' command Lukas Wagner
2026-04-15 11:58 ` [PATCH pve-storage 7/7] api: add /nodes/<node>/storage/<storage>/identity route Lukas Wagner
2026-04-17 8:54 ` Fiona Ebner
2026-04-17 9:11 ` 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=DHVBALQJTVEW.3J1RKLBCCGHJO@proxmox.com \
--to=l.wagner@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=pve-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.