I tried to launch an app using CDG for example and it failed because it wasn’t in the enum list on graphql.
Basing this on the region docs on the website, it looks like it’s missing 5 locations in the enum.
I tried to launch an app using CDG for example and it failed because it wasn’t in the enum list on graphql.
Basing this on the region docs on the website, it looks like it’s missing 5 locations in the enum.
Good catch, we’ll fix it.
@Carter should be fixed now!
Thanks!
Just a heads up, since it’s now a string type input, there might be some customers who’s integrations break if they’re using the graphql API. Each region now needs to be wrapped in quotes whereas before it had to be without.
Thanks for the heads up. It’s unfortunate, but an enum would be trouble over time anyway. Our regions change periodically and removing enum values that were in use will break clients instead of returning a validation error.