Hello PagerDuty community!
I wanted to propose an idea for an update ahead of pdpyras v4 that would actually help guide development of v4. An improvement I’m hoping to add to the library in v4, time permitting, is a new pagination method that is more resistant to race conditions and can be safely used for updating/deleting records en masse.
Would anyone strongly object to setting a custom user-agent HTTP header that identifies the client as pdpyras, including its version number and the Python version?
The reason I ask is because it would make it possible for PagerDuty to identify usage of this API client library, and thus in a certain sense, gather usage information that we previously did not gather.
For a more in-depth description of how and under what circumstances pagination can be affected by concurrent create/update/delete operations, see Issue #9 and also Disclaimers Regarding Iteration in the readme on the dev branch.
Update: the new version has been released! Versions 3.1 and later should set a distinct
User-Agent header in all requests.