Currently when I'm using the
VpsService API, there are some calls which return nothing. Some of these calls could return a sensible value.
OrderVpsInAvailabiltyZone for example: these calls return nothing, but they could return the name/identifier of the VPS that was just created (username-vpsXX). That way you would immediately know which VPS requires more work (like installing an OS, or adding add-ons), instead of having to sift through the output of
This will greatly improve the "quality of life" while using this API.
Here are my suggestions:
|Call||Preferred response||Other options|
|orderVps||Transip_Vps of new VPS||just the name|
|orderVpsInAvailabilityZone||""||just the name|
|cloneVps||""||just the name|
|cloneVpsToAvailabilityZone||""||just the name|
|cancelVps||date/time of cancellation||type of cancellation (end/immediately)|
|cancelAddon||date/time of cancellation||type of cancellation (end/immediately)|
|cancelPrivateNetwork||date/time of cancellation||type of cancellation (end/immediately)|
|orderPrivateNetwork||Transip_PrivateNetwork of new network||just the name|
|createSnapshot||Transip_Snapshot of created snapshot||just the name|
|addIpv6ToVps||string of all IPv6 addresses||-|
My main motivation for this request is for the
orderVpsInAvailabilityZone call, but in general this would be immensely helpful to get the object (like
Transip_Vps) or at the very least the identifier of each resource that was just created.
While we'd love to offer a feature like this, when you order a product we don't immediately have the name yet. The product name isn't assigned yet until a later stage, after various checks have been performed in our billing system and the order has been definitively approved.
For creating a snapshot and such it would however be possible. While we can't provide a date for implementation now, we'll be keeping this in mind for a future update.