On Fri, 05 Dec 2025 11:02:39 +0100, Dominik Csapak wrote:
> It seems, that 'alias' schema does not properly work currently for
> normal schema definitions (only for property-string), since it does not
> verification of the actual schema (checked by calling the api with
> maxworkers=1000, which throws no errors). Luckily, this is the only use
> of alias for api parameters that I could find. For the new cluster wide
> api calls it did not do anything, since we did not actually use
> `$param->{maxworkers}`, but for the node specific one broke the UI,
> since there we still send 'maxworkers', but the backend did not use that
> anymore.
>
> [...]
Applied, thanks!
[1/1] api: workaround broken 'maxworkers' alias in bulk actions api calls
commit: 60a0f0f0e81176c763f60c17c301791efda347d7
_______________________________________________
pve-devel mailing list
[email protected]
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
