You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I'll preface this with the fact that this is likely the wrong place for this issue, but wasn't 100 percent sure on where I should lodge this issue. Possibly should be here? https://github.com/digitalocean/openapi (please advise if this is the case).
Anyway, simply put, it seems that the Digital Ocean API is simply incapable of deleting default VPC's in a given account. Which is rather strange since on AWS and Vultr you can with their API's, which therefore means you can with their Terraform providers. There's a previous issue highlighting this here in a manner of speaking:
Effectively, I'd like to be able run a terraform destroy and have it be able to also destroy any and all VPC's including the defaults. Similar to many other providers out there. Personally, I've tested Vultr and AWS for this specific functionality, and it works flawlessly.
Describe alternatives you've considered
I suspect there isn't a whole lot to consider given the context and the fact that this appears to be a limitation of the API, which is the root cause of this issue.
The workaround I have used in the meantime is to have a separate tfvars and root module that handles "default" resources in a given account that never gets touched, so any other resources I create with yet another tfvars, root module and state file, means I can terraform destroy and terraform apply all day long without issues.
However, I really shouldn't need to do this IMO. I should, if I choose, be able to have one root module, tfvars and state per account and write my code in a dry manner so as to keep things simple and easy. Or any other arrangement for that matter.
Additional context
I've linked a previous issue below which mentions the fact that the Digital Ocean API cannot delete default VPC's.
Is your feature request related to a problem? Please describe.
I'll preface this with the fact that this is likely the wrong place for this issue, but wasn't 100 percent sure on where I should lodge this issue. Possibly should be here? https://github.com/digitalocean/openapi (please advise if this is the case).
Anyway, simply put, it seems that the Digital Ocean API is simply incapable of deleting default VPC's in a given account. Which is rather strange since on AWS and Vultr you can with their API's, which therefore means you can with their Terraform providers. There's a previous issue highlighting this here in a manner of speaking:
Issues
Describe the solution you'd like
Effectively, I'd like to be able run a
terraform destroy
and have it be able to also destroy any and all VPC's including the defaults. Similar to many other providers out there. Personally, I've tested Vultr and AWS for this specific functionality, and it works flawlessly.Describe alternatives you've considered
I suspect there isn't a whole lot to consider given the context and the fact that this appears to be a limitation of the API, which is the root cause of this issue.
The workaround I have used in the meantime is to have a separate tfvars and root module that handles "default" resources in a given account that never gets touched, so any other resources I create with yet another tfvars, root module and state file, means I can
terraform destroy
andterraform apply
all day long without issues.However, I really shouldn't need to do this IMO. I should, if I choose, be able to have one root module, tfvars and state per account and write my code in a dry manner so as to keep things simple and easy. Or any other arrangement for that matter.
Additional context
I've linked a previous issue below which mentions the fact that the Digital Ocean API cannot delete default VPC's.
Issues
The text was updated successfully, but these errors were encountered: