Terms threshold reported blank when assigning zero to it

[RubyLi0612]

Terraform Version

Terraform v0.9.11

Affected Resource(s)

newrelic_alert_condition

Terraform Configuration Files

# Configure the New Relic provider
provider "newrelic" {
  api_key = "${var.newrelic_api_key}"
}

resource "newrelic_alert_policy" "alert" {
  name = "Policy"
}

Expected Behavior

Assign threshold of the condition to 0 successfully.

Actual Behavior

Error outputed as: Terms threshold can't be blank

Steps to Reproduce

terraform apply

Important Factoids

According to the documentation for terraform newrelic_alert_condition, threshold can be set to 0:

Yet assigning it to "0", 0, "0.0" all trigger the error.

[grubernaut]

Upstream bug, submitted issue for a fix.

[RubyLi0612]

Hi. Thank you for fixing the issue. I tried the updated newest version of this provider (also included the newest paultyng/go-newrelic) by creating some NewRelic conditions. There were no more error reporting on this issue. However, when I get onto my NewRelic account to view them, I found that one APM BROWSER APPLICATION METRIC condition showed blank in the threshold box, which was set to "0" in terraform:

Yet another APM APPLICATION METRIC condition went fine. I'm guessing that there remains some issue for different types?

[grubernaut]

Hey @RubyLi0612, sorry you're still having an issue.

The fix above was only for the threshold attribute inside the terms configuration.
Can you elaborate on what you mean by:

I'm guessing that there remains some issue for different types?

Thanks!

[RubyLi0612]

Sorry for the confusion. I meant to say that the threshold attribute inside the terms configuration for a browser application metric condition I created seems not working. It is supposed to show 0 when I set 0 through terraform, but showed empty entry instead. However, apm application metric condition is correct.