You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I am learning Golang for a project, and wanted to ask something in comparison to the Python Library ngine-io/cs
So in the Python Library, I can create the VM, and it will return the vm details back right away even if it fails. I noticed that in the Go module, if you do a newVirtualMachineDeployment, if it creates the instance in error state it will return an error, leaving the broken VM in CloudStack.
This makes it impossible to have any automatic cleanup tasks (from what I've tried so far) on VMs that are failed. As we do not have the UUID. I could alter it with listVirtualMachines and provide the name as the keyword, but I do not like this idea in an automated fashion, as it could potentially delete something it shouldn't.
So my questions are
Is this how it was designed to work in CloudStack-Go?
Is there a way to get the vm details when it creates it in error?
I appreciate the support!
The text was updated successfully, but these errors were encountered:
So I am learning Golang for a project, and wanted to ask something in comparison to the Python Library ngine-io/cs
So in the Python Library, I can create the VM, and it will return the vm details back right away even if it fails. I noticed that in the Go module, if you do a newVirtualMachineDeployment, if it creates the instance in
error
state it will return an error, leaving the broken VM in CloudStack.This makes it impossible to have any automatic cleanup tasks (from what I've tried so far) on VMs that are failed. As we do not have the UUID. I could alter it with listVirtualMachines and provide the name as the keyword, but I do not like this idea in an automated fashion, as it could potentially delete something it shouldn't.
So my questions are
I appreciate the support!
The text was updated successfully, but these errors were encountered: