From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Fiona Ebner <f.ebner@proxmox.com>
Subject: [pve-devel] applied: [RFC storage 0/2] close #6669: plugin api: introduce on_update_hook_full() method
Date: Fri, 14 Nov 2025 00:41:51 +0100 [thread overview]
Message-ID: <176307723390.3062351.11352337263414135021.b4-ty@proxmox.com> (raw)
In-Reply-To: <20251008151140.127355-1-f.ebner@proxmox.com>
On Wed, 08 Oct 2025 17:11:30 +0200, Fiona Ebner wrote:
> The original on_update_hook() method is limited, because only the
> updated properties and values are passed in. Introduce a new
> on_update_hook_full() method which also receives the current storage
> configuration and the list of which properties are to be deleted. This
> allows detecting and reacting to all changes and knowing how values
> changed.
>
> [...]
Applied along side Friedrich's hint series, making this plugin API bump more
worthwhile, thanks!
[1/2] close #6669: plugin api: introduce on_update_hook_full() method
commit: 0b1331ccda6d1604147a8161137091af949c580c
[2/2] lvm plugin: disallow disabling 'snapshot-as-volume-chain' while a qcow2 image exists
commit: b6fefb03ba1ac408ba09d64dffaa7a5b776f2395
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-11-13 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 15:11 [pve-devel] " Fiona Ebner
2025-10-08 15:11 ` [pve-devel] [RFC storage 1/2] " Fiona Ebner
2025-10-08 15:11 ` [pve-devel] [RFC storage 2/2] lvm plugin: disallow disabling 'snapshot-as-volume-chain' while a qcow2 image exists Fiona Ebner
2025-11-13 23:41 ` 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=176307723390.3062351.11352337263414135021.b4-ty@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox