In order to delete a user, you must first remove them from any schedu… #40
Conversation
| self.log_entries = LogEntries(self.pagerduty, self) | ||
|
|
||
|
|
||
| class UserSchedules(Collection): |
There was a problem hiding this comment.
Did you find that this and UserEscalationPolicies was necessary? A quick test with the existing Schedules and EscalationPolicies collections seemed to work fine.
There was a problem hiding this comment.
So perhaps I've overlooked something, but it didn't seem like the Schedules allowed me to filter for only schedules that include a specific user?
There was a problem hiding this comment.
To be more clear, adding this
self.schedules = Schedules(self.pagerduty, self)
self.escalation_policies = EscalationPolicies(self.pagerduty, self)to the User container seemed to work without needing the two new collection classes you added.
|
Thanks for added this! I've wanted something like this but I haven't seen anything in the API docs. Do you have a reference where you found this was available? |
|
I poked the support people today asking why this isn't in the api. They told me it was, but undocumented. It will be documented 'soon'. :p |
or escalation policies they're in. You can find the schedules a particular user is in with api/v1/users/user_id/schedules. This is faster than grabbing all schedules and digging through to find a specific user.
|
ok, I made the changes you suggested and rebased to one commit. Any other changes? |
In order to delete a user, you must first remove them from any schedu…
|
Looks good. Thanks! I've pushed this to PyPI as pygerduty-0.32.1 |
…les they're in. You can find the schedules a particular user is in with api/v1/users/user_id/schedules. This is faster than grabbing all schedules and digging through to find a specific user.