Re: [PATCH v5 07/18] remote: New APIs for ThrottleGroup lifecycle management
On Mon, Nov 18, 2024 at 19:24:15 +0530, Harikumar R wrote:
I don't think we should do the 'change a subset of' semantics any more.
It was proven that it doesn't make sense. Specifically it's not possible
to distinguish between "I don't want to change this field" and "I
want
to delete/revert to default for this field".
The users must be instructed to always post the full required config.
If the customer provides only a subset of the throttle group, the other fields will remain
unchanged. Deleting/reverting a field may cause data mismatches between the XML and QEMU.
We will instruct users to always provide the full required configuration. Can we have a
validation to check the config?