Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Fix setting threshold and recurrence on update #67

Merged
merged 1 commit into from
Dec 16, 2019

Conversation

drubin
Copy link
Contributor

@drubin drubin commented Dec 3, 2019

This fixes setting the threshold and recurrence properties when a monitor changes.

Some things to note.

  1. I added this feature and totally forgot to implement this PR adding thresholds for alert contacts #18
  2. I couldn't find a way for us to check the alert contact's threshold and recurrence as part of the plan loop this will only work when you update the code/state. There is no way for this provider currently to detect a difference between the uptime robot config in uptime robot and this state.

@drubin
Copy link
Contributor Author

drubin commented Dec 16, 2019

@louy hi any update on this? I can also try remove the copy/paste block but I think it might be a bit over kill.

@louy
Copy link
Owner

louy commented Dec 16, 2019

Yeah don't worry about it. Let me get this merged and published

@louy
Copy link
Owner

louy commented Dec 16, 2019

Sadly can't add an automated test either because it would require a paid account. I guess we'd have to leave the test as is

@louy louy merged commit 078e134 into louy:master Dec 16, 2019
@drubin
Copy link
Contributor Author

drubin commented Dec 16, 2019

Thanks! I am more actively working on this I can try to revisit #57 I will contact uptimerobot directly and see what their support says.

@drubin drubin deleted the fix-update-contact branch December 16, 2019 14:36
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants