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
I think there has been a change in the UptimeRobot API recently, whenever I plan, any uptimerobot_alert_contact shows it needs to be replaced, showing the existing id matching the correct contact but the friendly name and type showing the first contact returned by the getAlertContacts
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# uptimerobot_alert_contact.webhook_website will be created
+ resource "uptimerobot_alert_contact" "webhook_website" {
+ friendly_name = "Webhook - Website"
+ id = (known after apply)
+ status = (known after apply)
+ type = "webhook"
+ value = "https://example.com"
}
Plan: 1 to add, 0 to change, 0 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
uptimerobot_alert_contact.webhook_website: Creating...
uptimerobot_alert_contact.webhook_website: Creation complete after 1s [id=6520503]
I then run plan again and get the following
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement
Terraform will perform the following actions:
# uptimerobot_alert_contact.webhook_website must be replaced
-/+ resource "uptimerobot_alert_contact" "webhook_website" {
~ friendly_name = "lorenzo - e-mail" -> "Webhook - Website"
~ id = "6520503" -> (known after apply)
~ status = "active" -> (known after apply)
~ type = "email" -> "webhook" # forces replacement
~ value = "[email protected]" -> "https://example.com" # forces replacement
}
Plan: 1 to add, 0 to change, 1 to destroy.
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value:
The text was updated successfully, but these errors were encountered:
the GetAlertContact function calls the getAlertContacts API with alert_contacts set to the ID of the contact....
except it's returning other contacts, 4 rather than all 12 contacts in my case, and then of course the code expects there to be 1 contact in the response
From a defensive programming point of view though, it is probably worth GetAlertContact confirming it only has 1 result, and the ID matches the expected result, probably there is similar potential in GetMonitor
I think there has been a change in the UptimeRobot API recently, whenever I plan, any uptimerobot_alert_contact shows it needs to be replaced, showing the existing id matching the correct contact but the friendly name and type showing the first contact returned by the getAlertContacts
I recreated this with a very basic setup
the plan was as expected
I then run plan again and get the following
The text was updated successfully, but these errors were encountered: