From: Dominik Csapak <d.csapak@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH datacenter-manager/yew-comp v2 0/5] add basic version guarding for pve guests config
Date: Tue, 2 Dec 2025 12:13:29 +0100 [thread overview]
Message-ID: <20251202111533.2068448-1-d.csapak@proxmox.com> (raw)
This adds some functionality so we can easily version guard specific features
for a pve node version.
Currently this is done for:
* env/entrypoint options for lxc
* intel-tdx options for qemu
We reuse the cached update information here, but we can easily change that out
if we want/need to.
changes from v1:
* use 'proxmox_deb_version::Version' instead of just cmp_version
(this makes the code a bit nicer)
* drop unrelated patch (was accidentally sent in v1)
proxmox-yew-comp:
Dominik Csapak (2):
pve: qemu: options/hardware: prepare and use version feature gating
pve: lxc panels: prepare/add version feature gating
Cargo.toml | 1 +
src/configuration/pve/lxc_dns_panel.rs | 6 ++++
src/configuration/pve/lxc_network_panel.rs | 6 ++++
src/configuration/pve/lxc_options_panel.rs | 32 ++++++++++++++++---
.../pve/lxc_resources_panel/mod.rs | 6 ++++
.../pve/qemu_hardware_panel/mod.rs | 6 ++++
src/configuration/pve/qemu_options_panel.rs | 32 ++++++++++++++++---
src/form/pve/lxc_property/mod.rs | 11 +++++++
src/form/pve/mod.rs | 10 +++---
9 files changed, 96 insertions(+), 14 deletions(-)
proxmxo-datacenter-manager:
Dominik Csapak (3):
lib/server: pve: add api call to get the cached version info from
remotes
ui: pve: qemu: load and pass the pve-manager version to panels
ui: pve: lxc: pass the pve-manager version to panels
lib/pdm-client/src/lib.rs | 6 ++++
server/src/api/pve/mod.rs | 21 ++++++++++++
server/src/remote_updates.rs | 22 ++++++++++++-
ui/src/lib.rs | 17 ++++++++++
ui/src/pve/lxc/mod.rs | 16 +++++++--
ui/src/pve/mod.rs | 63 ++++++++++++++++++++++++------------
ui/src/pve/qemu/mod.rs | 13 ++++++--
7 files changed, 133 insertions(+), 25 deletions(-)
Summary over all repositories:
16 files changed, 229 insertions(+), 39 deletions(-)
--
Generated by git-murpp 0.8.1
_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel
next reply other threads:[~2025-12-02 11:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-02 11:13 Dominik Csapak [this message]
2025-12-02 11:13 ` [pdm-devel] [PATCH yew-comp v2 1/2] pve: qemu: options/hardware: prepare and use version feature gating Dominik Csapak
2025-12-02 12:16 ` [pdm-devel] applied: " Thomas Lamprecht
2025-12-02 11:13 ` [pdm-devel] [PATCH yew-comp v2 2/2] pve: lxc panels: prepare/add " Dominik Csapak
2025-12-02 12:17 ` [pdm-devel] applied: " Thomas Lamprecht
2025-12-02 11:13 ` [pdm-devel] [PATCH datacenter-manager v2 1/3] lib/server: pve: add api call to get the cached version info from remotes Dominik Csapak
2025-12-02 11:46 ` Thomas Lamprecht
2025-12-02 12:17 ` [pdm-devel] applied: " Thomas Lamprecht
2025-12-02 11:13 ` [pdm-devel] [PATCH datacenter-manager v2 2/3] ui: pve: qemu: load and pass the pve-manager version to panels Dominik Csapak
2025-12-02 12:17 ` [pdm-devel] applied: " Thomas Lamprecht
2025-12-02 11:13 ` [pdm-devel] [PATCH datacenter-manager v2 3/3] ui: pve: lxc: " Dominik Csapak
2025-12-02 12:17 ` [pdm-devel] applied: " Thomas Lamprecht
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=20251202111533.2068448-1-d.csapak@proxmox.com \
--to=d.csapak@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