Closed jimmybrancaccio closed 3 years ago
I just tried to recreate this issue but my Droplet ended up in NYC3 as requested. I don't know why your attempt ended up in the wrong place.
@davidemyers Yeah, very weird!
I actually just tried creating another instance and selected NYC1 and it went there fine...I guess I should have tried NYC3 to see if I could replicate it, but it looks you were able to select NYC3 and have it deploy there without issue. 🤔
Describe the bug
When running through the deployment process, I've selected 1 for DigitalOcean and 8 for New York 3. However once deployment is complete I see the droplet has been created in Bangalore 1.
To Reproduce
Steps to reproduce the behavior:
./algo
. Select DigitalOcean as your cloud provider, and New York 3 as your region.Expected behavior
I would expect that the droplet would be deployed to the location from which I selected when running
./algo
.Additional context
N/A.
Full log