We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Good day,
We have a situation where two processes update Zendesk ticket and quite often step on each other's toes causing lost updates.
After doing some research, I found that ZD API indeed supports cooperative locking mechanism as described here: https://develop.zendesk.com/hc/en-us/articles/360059146153#protecting-against-ticket-update-collisions
It will be really great to have this supported in go-zendesk. WDYT?
The text was updated successfully, but these errors were encountered:
That's a really good idea :)
Sorry, something went wrong.
This PR #106 implements the safe_update
safe_update
No branches or pull requests
Good day,
We have a situation where two processes update Zendesk ticket and quite often step on each other's toes causing lost updates.
After doing some research, I found that ZD API indeed supports cooperative locking mechanism as described here: https://develop.zendesk.com/hc/en-us/articles/360059146153#protecting-against-ticket-update-collisions
It will be really great to have this supported in go-zendesk.
WDYT?
The text was updated successfully, but these errors were encountered: