An example of a relationship is Notification Rules, whose primary meaning is as a link between a user and a contact method. No individual notification rule has a unique, name-worthy meaning, and so they are handled (read and written) only as a collection. There is no compelling reason to update a single notification rule in place rather than replace the entire object with a new one. While this might seem like a significant loss of functionality, data shows that a trivially small number of clients outside of the PagerDuty web app are using it:
- over the last 30 days, only 11 requests were made to
PUT notification_rules/idusing non-cookie authentication, and all by the subdomainredacted. While the mobile team experimented with it in the latest "Edit Notification Rules" update in 3.6, they've confirmed that that endpoint isn't being used.
Similarly, the escalation rules relationship sees little in-place use:
- over the last 30 days, only one request was made to
PUT escalation_rules/idusing non-cookie authentication.