Add support for Custom DNS servers to prevent general destruction issues

[sknopp]

I've got a Custom DNS server setting linking behind one of my connected networks which has been declared as Terraform resource itself.

As there is no possibility to declare DNS servers by Terraform directly I've done this step by hand, but now the API-sided integration check crashes my TF setup when i try to destroy and re-apply my terraform configuration, because there is still an existing reference into my network which now prevents deletion.

So this is not just a feature request but more an actual issue which affects a core functionality for managing network resources.

[vladhss]

@sknopp Latest versions of terraform provider has cloudconnexa_settings resource where you can define dns servers

[sknopp]

Thanks for the hint, didn't notice their has been a patch. Awesome!

Unfortunately it's still pretty bad documented.

For example, when i try to set the default_region here i have no idea where to look up the list of possible values. In my case I want to select Amsterdam. So assuming from the examples like us-west-1 this is not alligned with the values documented here.

Sounds like Azure/AWS region strings?

Error message from the API is also still pretty generic:

Error: status code: 400, response body: {"errorMessage":"Http message not readable","statusError":"Bad Request"}

Looking forward to get this usable. 👍