Add transferEncoding for Streaming RequestBody with UnsignedPayload as True #5906
+1,758
−1
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.
Motivation and Context
The authType traits will be deprecated in favor of the unsignedPayload traits. Generators implementing this SEP must ignore the old traits if the new traits are present. If the new traits are not present, generators should fall back to using the old traits. The section above describes how backwards compatibility will be maintained.
Modifications
opModel.isUnsignedPayload()
while setting.transferEncoding(true)
on Streaming request body.unsignedPayload
and AythType :"V4_UNSIGNED_BODY
" so there was no impact even without fix, this fix is done for future model updates that will useunsignedPayload
and not d AythType :"V4_UNSIGNED_BODY
"Testing
Screenshots (if appropriate)
License