We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
provider version = 0.0.7
Disclaimer: this might be a bad idea.
I've got the following terraform configuration that applies successfully and works as expected:
data "honeycombio_trigger_recipient" "slack" { dataset = "my-very-special-datset" type = "slack" target = "#alerts" } resource "honeycombio_trigger" "trigger" { //query omitted recipient { id = data.honeycombio_trigger_recipient.slack.id } }
However, I receive the following when I run a plan/apply
~ recipient { id = "some-id" - target = "#alerts" -> null - type = "slack" -> null }
It would be nice if that diff could be suppressed without duplicating the recipient target and type.
The text was updated successfully, but these errors were encountered:
Ah good call. This can be fixed by setting target and type as computed fields. In this case Terraform also accepts changes coming from the API.
target
type
Looking at the schema, id is computed but the other two fields of a recipient aren't.
id
Sorry, something went wrong.
Add test case for #26
b813002
2471d83
Didn't intend to push to main straight away, but this is fixed now 😅
No branches or pull requests
provider version = 0.0.7
Disclaimer: this might be a bad idea.
I've got the following terraform configuration that applies successfully and works as expected:
However, I receive the following when I run a plan/apply
It would be nice if that diff could be suppressed without duplicating the recipient target and type.
The text was updated successfully, but these errors were encountered: