Changing recipient details for Slack type recipient in honeycombio_trigger causes 422 failure

[watsonm-drivevariant]

Versions
0.13.0 & 0.14.0

Steps to reproduce

1. Create a simple terraform alert

main.tf:

data "honeycombio_query_specification" "query_specification" {
    calculation {
        op = "MAX"
        column = "metrics.cpu.usage"
    }

    filter { 
        column = "label.app"
        op = "="
        value = "jazz-backend-api"
    }
    time_range = 300
}

resource "honeycombio_query" "trigger_query" {
    dataset = "kubernetes-metrics"
    query_json = data.honeycombio_query_specification.query_specification.json
}

resource "honeycombio_trigger" "trigger" {
    name = "honeycomb-bug"
    description = "Created to reproduce observed honeycomb bug"
    query_id = honeycombio_query.trigger_query.id
    dataset = "kubernetes-metrics"
    frequency = 300
    alert_type = "on_change"
    threshold {
        op = ">"
        value = 0.9
    }
    recipient {
      type = "slack"
      target = "#my-alerting-channel"
    } 
}

settings.tf:

terraform { 
    required_providers { 
        honeycombio = {
            source = "honeycombio/honeycombio"
            version = "~> 0.14.0"
        }
    }
    required_version = "~> 1.1.7"
}

provider "honeycombio" {
}

Run terraform init and terraform apply to create alert. Answer prompts for api key, etc.

2. Modify the target in the recipient block

 ...
  recipient {
    type = "slack"
    target = "#my-alerting-channel-2"
  }

3. Once again, run terraform apply to make changes to the trigger.

The apply will create a plan

Terraform will perform the following actions:

  # honeycombio_trigger.trigger will be updated in-place
  ~ resource "honeycombio_trigger" "trigger" {
        id          = "pweHeSfZh9q"
        name        = "honeycomb-bug"
        # (6 unchanged attributes hidden)

      ~ recipient {
            id     = "m7wahgjr9SC"
          ~ target = "#my-alerting-channel" -> "#my-alerting-channel-2"
            # (1 unchanged attribute hidden)
        }

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

but fail when attempting to apply

╷
│ Error: 422 Unprocessable Entity: unknown recipient - check recipient id 'm7wahgjr9SC' values.
│ 
│   with honeycombio_trigger.trigger,
│   on main.tf line 20, in resource "honeycombio_trigger" "trigger":
│   20: resource "honeycombio_trigger" "trigger" {
│ 
╵

Additional context
Terraform version 1.1.7

I would expect to be able to use the same basic structure to both create triggers with slack recipients, and update the recipient later to go to a new channel if necessary. The issue above poses problems when attempting to use input variables to fill trigger details while creating multiple triggers. Especially when it is not known ahead of time which recipients already exist and which do not.

[jharley]

Thank you for taking the time to report this.

This is another manifestation of the buggy state of these recipient blocks.

Related to #200, #263, and #267

[jharley]

Fix released in v0.15.0