This repository has been archived by the owner on Mar 12, 2023. It is now read-only.
Add ZenEx.Model.User.permanently_destroy #23
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In order to be GDPR compliant, one must delete a user permanently after deleting the user. This PR adds ZenEx.Model.User.permanently_destroy, which must be called with the id of a user has been previously destroyed.
otoyo
approved these changes
Jun 22, 2022
|
Thank you for the patch 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to be GDPR compliant, one must delete a user permanently after
deleting the user.
This PR adds ZenEx.Model.User.permanently_destroy, which must be called
with the id of a user who has been previously destroyed.
See https://developer.zendesk.com/api-reference/ticketing/users/users/#permanently-delete-user.