Seeing a large number of HTTP "GOAWAY" errors when refreshing NS1 resources.

[RussellRollins]

When we run a Terraform plan of our NS1 resources, we see a large number of HTTP "GOAWAY" error responses from the NS1 API servers. This seems to be a new problem, we only started experiencing this within the last month, for the same Terraform configuration.

Terraform Version

0.12.24, sorry, I know it's old, but I don't think it's relevant to the issue.

ns1 provider version is: 1.12.2

Affected Resource(s)

Please list the resources as a list, for example:

• ns1_zone
• ns1_record

Terraform Configuration Files

variable "ns1_apikey" {}

provider "ns1" {
  apikey                 = var.ns1_apikey
  version                = "1.12.2"
  rate_limit_parallelism = 80
}

resource "ns1_zone" "my_zone_com" {
  zone                   = "myzone.com"
  refresh                = 3600
  ttl                    = 600
  expiry                 = 604800
  retry                  = 600
  autogenerate_ns_record = true
}

resource "ns1_record" "my_zone_com_mx_records" {
  zone   = "myzone.com"
  domain = "myzone.com"
  type   = "MX"
  ttl    = "3600"
  answers {
    answer = "10 aspmx.l.google.com"
  }
}

// ... and many more ...

Expected Behavior

Terraform is able to refresh the NS1 Zones and Records

Actual Behavior

Error: Get \"https://api.nsone.net/v1/zones/myzone.com/foo.email.myzone.com/A\": http2: server sent GOAWAY and closed the connection; LastStreamID=2083, ErrCode=PROTOCOL_ERROR, debug=\"\"\n\n\n\n

Steps to Reproduce

1. terraform plan