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
Related: Azure/autorest.csharp#786 Related: Azure/autorest.csharp#792
We had logic to only process a single response as an 'initial' response and another response as a 'final' response. So, max number of processed responses for LRO was 2. In the PR related, we allowed all responses to be processed so that we had a complete list of status codes. You can see the example from Compute here: https://github.com/Azure/azure-rest-api-specs/blob/945ce9037b678447f0a3322a1ba669856d0b9468/specification/compute/resource-manager/Microsoft.Compute/stable/2019-12-01/compute.json#L3666-L3675
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Related: Azure/autorest.csharp#786
Related: Azure/autorest.csharp#792
We had logic to only process a single response as an 'initial' response and another response as a 'final' response. So, max number of processed responses for LRO was 2. In the PR related, we allowed all responses to be processed so that we had a complete list of status codes. You can see the example from Compute here: https://github.com/Azure/azure-rest-api-specs/blob/945ce9037b678447f0a3322a1ba669856d0b9468/specification/compute/resource-manager/Microsoft.Compute/stable/2019-12-01/compute.json#L3666-L3675
The text was updated successfully, but these errors were encountered: