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
Add email_filters to pagerduty_service_integration of type generic_email_inbound_integration #88
Comments
We were hit by this one as well. If there is support for this one, we might build it. It might be nicer if the resource didn't have the email specific stuff at the top-level since it really only applies to the email thing. Maybe a specific |
At the very least can we get the ability to set the Email Management config? These are the values for email_incident_creation
I would also like to be able to set the custom emails rules. But looking at what is configured in the API I can appreciate how complicated the integration resource would become, all for one option, of one option, of an integration. I think a dedicated email integration resource might be simpler. |
If it helps here is the payload I used for testing updating a custom rules via the API for my PRTG email integration
|
email_incident_creation for pagerduty_service_integration would indeed be useful to many orgs |
I'm trying to migrate my PRTG PagerDuty configuration to Terraform, I'm stuck on this as well. Any updates on this? |
Same here. It's painful to manually create PRTG integration for many services. |
Same here |
Hi there,
I am using the
generic_email_inbound_integration
type ofpagerduty_service_integration
.Being as it is, I heavily depend on some email filtering.
The pagerduty API itself seems to be a bit underdocumented (can't find a schema for this) but below is roughly the response of my manually created service integration.
https://api.pagerduty.com/services/__service__/integrations/__integration__
Would you be interested in adding
email_filters
into your PagerDuty provider?Cheers, Mathias
The text was updated successfully, but these errors were encountered: