[pve-devel] [PATCH manager v3] ui: improve user experience for vm/container transfer between pools
Thomas Lamprecht
t.lamprecht at proxmox.com
Wed Sep 13 07:58:47 CEST 2023
Am 08/09/2023 um 15:18 schrieb Philipp Hufnagl:
> After the implementation of fix #474, it has been suggested that
> instead of requiring the user to click a checkbox allowing migration,
> it should be allowed automatically and and a warning should be displayed
>
> Further it has been discussed to rename the feature from "transfer" to
> "migrate". However and API change would break already implemented usage
> and so it has been decided to call it (for now) transfer everywhere to
>
> Signed-off-by: Philipp Hufnagl <p.hufnagl at proxmox.com>
> ---
Missing description of changes since previous patch version here.
Also missing defining the API defaults like asked multiple times, but I
pushed out a changeset [0] to address most of this on Friday before you
sent the v2, so that I was able to bump pve-manager for some other, a
bit pressing, bug fixes w.r.t. notifications stuff that Lukas sent in a
timely manner.
After rethinking it, I also renamed the APÌ parameter. As the package
that added the new parameter was only on pvetest I saw no real concerns
for practical ABI breakage, especially as this is a bit of a niche feature
(so @all please do not use this as general precedence, such things should
be considered case-by-case).
[0]: https://git.proxmox.com/?p=pve-manager.git;a=shortlog;h=57490ff2c6a38448d511d32ec1b4c9bc825545d9
More information about the pve-devel
mailing list