can't set priority to 0 for mx in digitalocean_record

[hashibot]

This issue was originally opened by @dmitryint as hashicorp/terraform#5069. It was migrated here as part of the provider split. The original body of the issue is below.

---

Terraform v0.6.11

resource "digitalocean_record" "mx_1" {
    domain = "host.com"
    type = "MX"
    priority = 0
    value = "mx.host.com."
}

When I try to set the priority 0 MX record occurs error message.

Failed to create record: POST https://api.digitalocean.com/v2/domains/host.com/records: 422 Priority is not a number and Priority Priority must be an integer between 0 and 65535

When I changing the priority to another number, e.g. 10, then everything is OK.

Same problem with weight

[hashibot]

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

[andrewsomething]

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.

[KibaFox]

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).

[andrewsomething]

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!