specs, add test for LongRunningRpcOperation #242
Conversation
|
| Expected status code: 202 | ||
| Expected response header: operation-location={endpoint}/different-poll-result/jobs/operations/operation1 | ||
| Expected response header: location={endpoint}/different-poll-result/jobs/job1 | ||
| Expected response body: | ||
| ```json | ||
| { | ||
| "operationId": "operation1", | ||
| "status": "InProgress" | ||
| } | ||
| ``` |
There was a problem hiding this comment.
Added a case of polling location/result is different from final resource location/result.
OperationResourcePollingStrategy in Java supports this legacy scenario. However it is possible not all SDK supports it.
Also, the result of getLroMetadata API call would be confused on the logicalResult or finalStep (I am not yet sure whether it means tsp need to written differently, or there is bug in getLroMetadata).
Hence it likely need adjustment, after the LongRunningRpcOperation been put to Azure.Core.
weidongxu-microsoft
requested review from
timotheeguerin,
iscai-msft,
lmazuel,
nguerrera and
tjprescott
as code owners
Cadl Ranch Contribution Checklist:
@scenarionames. Someone can look at the list of scenarios and understand what I'm covering.@scenarioDocs for extra scenario description and to tell people how to pass my mock api check.