can't set priority to 0 for mx in digitalocean_record about terraform-provider-digitalocean HOT 4 CLOSED

This comment was originally opened by @stack72 as hashicorp/terraform#5069 (comment). It was migrated here as part of the provider split. The original comment is below.

This is due to a known issue and will be worked on in #5694

from terraform-provider-digitalocean.

This happens because godo was dropping the 0 as an empty value when marshalling to JSON. This was addressed in: digitalocean/godo#164 So a newer version of godo needs to be vendored.

from terraform-provider-digitalocean.

I'm running into this issue too. Unfortunately, digitalocean/godo#164 was merged into that project's master branch after v1.3.0 was tagged (the latest tagged release currently).

from terraform-provider-digitalocean.

I'm happy to say that yesterday, we release version 1.0.0 of the DigitalOcean Terraform provider. It should include a fix for this issue.

You can find the full changelog here: https://github.com/terraform-providers/terraform-provider-digitalocean/blob/master/CHANGELOG.md#100-september-27-2018

In order to upgrade an existing project to the latest version, run:

terraform init -upgrade

If you believe that this issue is being closed by mistake or the problem has not been resolved, please let me know or feel free to open a new issue with additional details.

Thanks for your patience!

from terraform-provider-digitalocean.