catborise 8d7f28482f fix(api): VM API answers as the VM pages do ... - A VM delete reads delete_disk and delete_nvram as booleans from a JSON or form body. The view read them as HTML checkboxes from the form body only: JSON {"delete_disk": true} kept the disks while reporting success, and a form "delete_disk=false" deleted them. Refused options stop nothing; the API schema names both options. - Power on and power cycle of a template answer 409 instead of reporting a start that did not happen. - The VM details leave out the host's ISO images for non-superusers, as the VM page does; reading them also refreshed every pool of the host. - Flavors take values of at least 1, as the web form does, and show their id for later changes; a migration needs neither live nor offline; a VM create on an unknown compute answers 404 instead of 500.		2026-10-26 17:47:18 +03:00
..
serializers.py	fix(api): VM API answers as the VM pages do	2026-10-26 17:47:18 +03:00
viewsets.py	fix(api): VM API answers as the VM pages do	2026-10-26 17:47:18 +03:00