-
Notifications
You must be signed in to change notification settings - Fork 240
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 ability to create or update integrations with email filter rules #315
Comments
@gerardocorea I'm an outside contributor to this repo, but PagerDuty has set a policy of not supporting undocumented API features in the client. As best I can tell the field you refer to isn't documented on that URL, and so we cannot support this functionality until they add documentation for it. @stmcallister would you be able to also relay the request that this be documented? |
Sounds good, I have a working version of this which im sure could use some feedback. If there also a way in which I can contribute back the documentation please feel free to let me know. |
@gerardocorea sorry that I missed your question before now. As I recall, that's something that internal product folks at PagerDuty need to do. I had asked the same question once. 😉 |
Good news, this is documented now! I'll make this part of the WIP v1.5.0 release. https://developer.pagerduty.com/api-reference/b3A6Mjc0ODIwMw-create-a-new-integration |
I raised #385 to address this feature request. |
The pagerduty api supports fields for email integrations that allows specification from regex's and how to handle creation of incidents. Adding in structs for these properties can make it easier to manage these rules.
https://developer.pagerduty.com/api-reference/reference/REST/openapiv3.json/paths/~1services~1%7Bid%7D~1integrations~1%7Bintegration_id%7D/put
Example API call that can be used below.
The text was updated successfully, but these errors were encountered: