Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Providing a Slack Channel ID for trigger target returns an error. #533

Closed
scgerkin opened this issue Aug 15, 2024 · 2 comments · Fixed by #540
Closed

Providing a Slack Channel ID for trigger target returns an error. #533

scgerkin opened this issue Aug 15, 2024 · 2 comments · Fixed by #540

Comments

@scgerkin
Copy link

scgerkin commented Aug 15, 2024

We're using Terraform to manage a few Honeycomb triggers and recently changed a channel name which necessitated needing to update the trigger targets. After testing in the UI, I was able to successfully send a test trigger to the new channel by using the Channel ID rather than the #channel-name. However, the Terraform provider doesn't like this:

Error: Error Updating Honeycomb Trigger

  on k8s_triggers.tf line 206, in resource "honeycombio_trigger" "k8s_pods_pending_spike":
 206: resource "honeycombio_trigger" "k8s_pods_pending_spike" {

recipients: (0: (target: slack target must begin with '#' or '@'.).).

Versions

0.18.0 and 0.26.0

Steps to reproduce

Attempt creating a honeycombio_trigger as:

resource "honeycombio_trigger" "my_trigger" {
  name        = "My trigger"
  description = "My desc"

  query_id = honeycombio_query.my_query.id
  dataset  = "my-dataset"

  frequency = 60

  alert_type = "on_change"

  threshold {
    op    = ">="
    value = some_val
  }

  recipient {
    type   = "slack"
    target = "C1234"
  }
}

Additional context

n/a

@jharley jharley added the bug label Aug 15, 2024
@jharley
Copy link
Collaborator

jharley commented Aug 15, 2024

Hey, @scgerkin! Thanks for raising this.

We're aware of this issue (and discrepancy with the UI) and are currently working on improving the Slack integration. This limitation is in the underlying API -- not just the provider -- and is included the scope of our work.

@jharley jharley added improvement and removed bug labels Aug 15, 2024
@jharley jharley added the blocked This issue is blocked by something external. label Aug 23, 2024
@jharley jharley removed the blocked This issue is blocked by something external. label Sep 3, 2024
@jharley
Copy link
Collaborator

jharley commented Sep 3, 2024

Support for providing channel IDs was just released in v0.27.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants