terraform-provider-iterative
terraform-provider-iterative copied to clipboard
Simplify bucket emptying mechanism
Follow-up of #420 and #453, closes #459
It turns out that #459 happened because when some resources are already missing, t.Read() fails and the emptying logic never runs. Still, needs extensive testing before merging.
@0x2b3bfa0 seems to be failing in GCP
The bucket you tried to delete is not empty.", Details:[]interface (nil), Body:""error":"code":409,"message":"The bucket you tried to delete is not empty.","errors":["message":"The bucket you tried to delete is not empty.","domain":"global","reason":"conflict"]", Header:http.Header(nil), Errors:[]googleapi.ErrorItemgoogleapi.ErrorItemReason:"conflict", Message:"The bucket you tried to delete is not empty."***
Ditto: https://github.com/iterative/terraform-provider-iterative/pull/471#issuecomment-1084526316