You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
FYI - this appears to be a limitation of the UptimeRobot service's API, as they don't allow you to create PagerDuty AlertContact types (https://uptimerobot.com/api/): alertcontact>type | 1 - SMS2 - E-mail3 - Twitter DM4 - Boxcar5 - Web-Hook6 - Pushbullet7 - Zapier9 - Pushover10 - HipChat11 - Slack | the type of the alert contact notified (Zapier, HipChat and Slack are not supported in the newAlertContact method yet).
You can query existing PagerDuty AlertContact values, and it will tell you that they are "type":16 - however attempting to submit a newAlertContact with type 16 results in: {"stat":"fail","error":{"type":"invalid_parameter","parameter_name":"type","passed_value":"16","message":"type is invalid."}}
So until UptimeRobot's API allows the creation of PagerDuty AlertContact types, there's not much this TF provider can do.
Update: the UptimeRobot service's API now supports PagerDuty (as well as other new types of) AlertContact values. So this should be possible to implement now!
Please add pagerduty as an available contact type for the uptimerobot_alert_contact resource.
Thanks!
The text was updated successfully, but these errors were encountered: