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.

Sign up for GitHub

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

Jump to bottom

Changing recipient details for Slack type recipient in honeycombio_burn_alert causes 422 failure #322

Closed
hdenman-stripe opened this issue Jun 15, 2023 · 1 comment · Fixed by #346
Closed

Changing recipient details for Slack type recipient in honeycombio_burn_alert causes 422 failure #322

hdenman-stripe opened this issue Jun 15, 2023 · 1 comment · Fixed by #346
Labels
bug

Comments

@hdenman-stripe
Copy link

Versions
0.13.1, 0.15.1

Steps to reproduce
This is just the same as #303, except that it pertains to honeycombio_burn_alert rather than honeycombio_trigger

Additional context
I'm sorry I don't have a minimal repro; I use terraform behind a wrapper, rather than directly.
@jharley jharley added the bug label Jun 20, 2023
@jharley
Copy link
Collaborator

jharley commented Jun 20, 2023

Related to #263

@jharley jharley mentioned this issue Aug 21, 2023
Merged
@jharley jharley linked a pull request Aug 21, 2023 that will close this issue
honeycombio_burn_alert - migrate resource to Plugin Framework #346
Merged
jharley added a commit that referenced this issue Aug 23, 2023
@jharley
honeycombio_burn_alert - migrate resource to Plugin Framework (#346)
b4269f8 
In a similar fashion to the work done for v0.15.0 for
`honeycombio_trigger`, this migrates `honeycombio_burn_alert` to the
~new Plugin Framework to squash the similar set of bugs and annoyances
around `recipient` blocks.

Closes #263, #322
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
2 participants
@jharley @hdenman-stripe