DO Ideas 2

Always include all regions in the /regions API call

The Amsterdam region/datacenter is not accepting new droplet creation and so your API is not returning Amsterdam in the /region call.

It's important to include all regions/datacenters in this call in order to not break linkages to pre-existing droplets. Instead, perhaps include a status identifier indicating that it is offline/unavailable for new droplet creation.

  • Nico
  • Sep 11 2018
  • Shipped
  • Sep 11, 2018

    Admin Response

    Hi all! We've recently release version 2 of our API into public beta. This includes adding an "available" boolean attribute to the region objects. Check out the documentation: While the beta is on-going, we’re looking for as much feedback as possible. If there’s anything else you’d like to see in the API, please open an issue over on our GitHub page: Thanks!
  • Attach files
  • TomS commented
    September 11, 2018 18:21

    A note for those finding this is the future. While this attribute has been added it does not *currently* address the request. Two regions, AMS2 and SFO1, recently had droplet creation disabled due to resource constraints and they were removed from the API results for """.

  • Marek Jalovec commented
    September 11, 2018 18:21

    This would be very nice, its not possible to display correct info about older droplets. Please add older items and add some flag to them.

  • Anonymous commented
    September 11, 2018 18:21

    Today my application broke down because ams1 was removed from the regions! I hope they would add it soon.

  • Nico commented
    September 11, 2018 18:21

    Same issue with the /Images call. I can't find out what distribution my droplet is running because it was deployed using a CentOS image which is no longer "available" for droplet creation.