From: Hannes Laimer <h.laimer@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] superseded: [PATCH proxmox{, -datacenter-manager} 0/4] generate Vec's for string-lists
Date: Fri, 24 Oct 2025 16:44:09 +0200 [thread overview]
Message-ID: <22c40700-6e4b-4515-8560-ff68e4eecb2a@proxmox.com> (raw)
In-Reply-To: <20251021135018.88877-1-h.laimer@proxmox.com>
superseded-by:
https://lore.proxmox.com/pdm-devel/20251024144250.145205-1-h.laimer@proxmox.com/T/#t
On 10/21/25 15:50, Hannes Laimer wrote:
> PVE does accept actual arrays[1] as input to fields with a `-list` format.
> This updates the generator so it produces a Vec if it is a parameter,
> not for return values.
>
> I did not find endpoint that directly share the same format for
> parameters and return value. Update endpoint also include a
> `delete`-field and those were the only ones that had really similar
> input and output formats. So deduplication in the generate _should_ not be
> a problem here.
>
> This required some small changes to pdm. Context for those is in the
> commit itself.
>
> [1] pve-common 69d9edcc ("section config: implement array support")
>
>
> proxmox:
>
> Hannes Laimer (3):
> pve-api-types: schema2rust: generate arrays for types with format
> `-list`
> pve-api-types: add regex for both storage- and bridge-pair
> pve-api-types: regenerate
>
> pve-api-types/generate.pl | 11 +-
> pve-api-types/generator-lib/Schema2Rust.pm | 35 ++-
> pve-api-types/src/generated/code.rs | 2 +-
> pve-api-types/src/generated/types.rs | 335 +++++++++++----------
> pve-api-types/src/types/verifiers.rs | 10 -
> 5 files changed, 213 insertions(+), 180 deletions(-)
>
>
> proxmox-datacenter-manager:
>
> Hannes Laimer (1):
> server: use types indead of string for migration parameters
>
> server/src/api/pve/lxc.rs | 133 ++++++++----------------------------
> server/src/api/pve/qemu.rs | 135 ++++++++-----------------------------
> 2 files changed, 56 insertions(+), 212 deletions(-)
>
>
> Summary over all repositories:
> 7 files changed, 269 insertions(+), 392 deletions(-)
>
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
prev parent reply other threads:[~2025-10-24 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-21 13:50 [pdm-devel] " Hannes Laimer
2025-10-21 13:50 ` [pdm-devel] [PATCH proxmox 1/3] pve-api-types: schema2rust: generate arrays for types with format `-list` Hannes Laimer
2025-10-21 13:50 ` [pdm-devel] [PATCH proxmox 2/3] pve-api-types: add regex for both storage- and bridge-pair Hannes Laimer
2025-10-21 13:50 ` [pdm-devel] [PATCH proxmox 3/3] pve-api-types: regenerate Hannes Laimer
2025-10-21 13:50 ` [pdm-devel] [PATCH proxmox-datacenter-manager 1/1] server: use types indead of string for migration parameters Hannes Laimer
2025-10-24 14:44 ` Hannes Laimer [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=22c40700-6e4b-4515-8560-ff68e4eecb2a@proxmox.com \
--to=h.laimer@proxmox.com \
--cc=pdm-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