PagerDuty notification recipients don't handle default computed value about terraform-provider-honeycombio

[adamdecaf]

We've ran into this too.

│ Error: Provider produced inconsistent result after apply
│ 
│ When applying changes to
│ module.wrathofcron.module.wrathofcron.honeycombio_trigger.triggers["critical_errors"],
│ provider "provider[\"registry.terraform.io/honeycombio/honeycombio\"]"
│ produced an unexpected new value: .recipient: planned set element
│ cty.ObjectVal(map[string]cty.Value{"id":cty.StringVal("9KiCzVXtxaj"),
│ "notification_details":cty.ListValEmpty(cty.Object(map[string]cty.Type{"pagerduty_severity":cty.String})),
│ "target":cty.UnknownVal(cty.String), "type":cty.UnknownVal(cty.String)})
│ does not correlate with any element in actual.
│ 
│ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.

[Vamsi-Mundra]

We've ran into this too.

Error: Provider produced inconsistent result after apply
When applying changes to honeycombio_trigger.routing_canary_cedar_request_latency_warning["production"], provider "provider[\"registry.terraform.io/honeycombio/honeycombio\"]" produced an unexpected new value: .recipient: planned set element cty.ObjectVal(map[string]cty.Value{"id":cty.StringVal("r9skJ6ZBv1C"), "notification_details":cty.ListValEmpty(cty.Object(map[string]cty.Type{"pagerduty_severity":cty.String})), "target":cty.UnknownVal(cty.String), "type":cty.UnknownVal(cty.String)}) does not correlate with any element in actual.
This is a bug in the provider, which should be reported in the provider's own issue tracker.