Open MartinZvelebil opened 1 day ago
Forgot to add to the code - if anywhere I put the .result() - directly on the restore_operation or later on - is always null + the missing methods for retrieving other atributes cannot really be described anyway. From other examples, it seems, that it should return everything needed, for example here.
Thanks for the feedback, we’ll investigate asap.
Describe the bug There are multiple things that are wrong regarding the backup_client.restores.begin_trigger. 1) For the IaasVMRestoreRequest, there is recover_point_id, but actually it is .name and not .id - missconception 2) When restore is triggered, there is no way how to get any particular information about the restore (for example JobID). I need to get information what was restored (disk objects), so atleast the JobID is needed. The only working method is .status() but for other atributes in the response body methods are totally missing. I would assume that .result() will help me with that, but that is also problem since it always returns Null 3) When the restore ends up in Succesfull state, the response does not even contain body anymore, since the token used in the request URL is already dead. Which means that response is with code 204.
To Reproduce
Expected behavior 1) Should be clear - missnamed 2) I don't think it should respond with Null always to the .result(). It should give us back the response as an object for example (for the response see below). I need to get the disks, that were recovered, so I can further work with them (mount them etc.).
Screenshots From this response, I can get only status with the .status(). So once the restores.begin_trigger is finished I can only tell it is finished, but I cannot work further with the retrieved disks. Properties, name etc. is not reachable.
If there is anything I missunderstood I would appreciate any help. Thank you and have a great day!