DO Ideas 2

Provide proactive notification & status page updates when Regions are disabled

Recently AMS2 and SFO1 had the creation of droplets disabled due to resource constraints. This caused breakage in some of my Terraform automation. While troubleshooting why these regions were unavailable I could find no references to any issues on the status page. When I directly queried the API ( https://api.digitalocean.com/v2/regions ) I saw that the regions were not being returned.

"curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer my_token_here" "https://api.digitalocean.com/v2/regions" | jq .regions[].slug"

"nyc1"
"sgp1"
"lon1"
"nyc3"
"ams3"
"fra1"
"tor1"
"sfo2"
"blr1"

This does not match the expectations set by the following links concerning the 'available' element:
https://digitalocean.uservoice.com/forums/136585-digitalocean/suggestions/4197795-always-include-all-regions-in-the-regions-api-cal

https://developers.digitalocean.com/documentation/v2/#regions

Please consider:
1. Providing proactive notification when disabling regions so that we can take action before we destroy our existing droplets.

2. Including the fact that these regions are disabled on the Status page. The only place I could find anything was by manually creating a droplet and seeing that the region was unavailable. For many of us that is not how we consume your service.

3. Either return the regions as 'disabled' or similar in the 'available' element of the regions API mentioned above or update the documentation so as to manage expectations.

Thank you.

  • TomS
  • Sep 11 2018
  • Attach files