-
Notifications
You must be signed in to change notification settings - Fork 299
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow operation to be blocking #146
Comments
Hey @djsly, can you elaborate on what's causing the issue here? |
Hi @mauricio , sure, the issue started last week, where the deletion of the volume (storage) started returning 409. An error about the volume still being attached to a droplet. So, even though we delete the droplet using the API, we get a 204 request, it was possible before to issue a deletion of the volume right away. Not we have to wait 3-4 sec for the droplet to be deleted for real on the DO side before the volume be we deleted properly. It would be beneficial that all DELETION requests would return the 204 once and only once the deletion process is completed.
|
@djsly fixed the issue himself at https://github.com/terraform-providers/terraform-provider-digitalocean/pull/22 |
https://github.com/terraform-providers/terraform-provider-digitalocean/issues/19
Has you can see, recently a change in the logic from the API at DO caused some issues with 3rd party app using the GODO product.
It would make sense that the GODO allow calls to be blocking, avoiding the different 3rd party app from doing polling and checking for statuses.
The text was updated successfully, but these errors were encountered: