Fixed bug in sip routing. SDK shouldnt send empty patch. #27919
Merged
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.
Description
Recently, we found bug in sending PATCH for sip configuration. When the trunks dictionary on the backend is already empty and user tries to call set_trunks with empty list, the API returns 422, unproccessable entity, because the PATCH request has empty body. This happens, because for trunks dictionary, we're using merge patch.
To fix this, check was added, to send the PATCH only if there are any trunks, that changed.
Scenarios for set_routes don't have this problem, as routes list is always completely replaced and not merge patched.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:
General Guidelines and Best Practices
Testing Guidelines