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
By default, the StatusCake API (beta) paginates uptime & SSL checks in blocks of 25. So currently if an account has >25 uptime checks, if the check that Ansible is searching for isn't found on the first page, it believes the check doesn't exist and will create a new entry:
"All uptime checks in StatusCake: %s", self.response.json()["data"]
)
returnself.response.json()["data"]
return []
This creates duplicate entries if the check does indeed exist beyond the first page. #38 increases the page size to 100, to fix the immediate issue, but in the future, the fetch_all method should probably support pagination.
The text was updated successfully, but these errors were encountered:
By default, the StatusCake API (beta) paginates uptime & SSL checks in blocks of 25. So currently if an account has >25 uptime checks, if the check that Ansible is searching for isn't found on the first page, it believes the check doesn't exist and will create a new entry:
ansible-collection-caktus-hosting-services/plugins/module_utils/statuscake.py
Lines 73 to 80 in b082d4a
This creates duplicate entries if the check does indeed exist beyond the first page. #38 increases the page size to 100, to fix the immediate issue, but in the future, the
fetch_all
method should probably support pagination.The text was updated successfully, but these errors were encountered: