Issue with [operationalinsights] / API Version [2021-06-01] - LRO operation does not expect 202 status code

[ziyeqf]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Service Used

loganalytics

API Versions Used

2021-06-01

Description

The method is only expecting HTTP 200, code link, while it's a LRO, and it will return HTTP 202. I assume it's a Swagger issue, so I opened one for that: Azure/azure-rest-api-specs#26678
But just a thought if we can add 202 to ExpectedStatusCodes for LROs when generating the sdk?

References

No response

[tombuildsstuff]

@ziyeqf

But just a thought if we can add 202 to ExpectedStatusCodes for LROs when generating the sdk?

In this case the data needs to be updated, as you've done in this PR however we can look to add a Data Workaround for this in the interim to workaround this issue - until the upstream issue is resolved.

I've added the upstream PR to our list of open issues fwiw, so we can track that on there 👍

[tombuildsstuff]

Fixed via hashicorp/pandora#3478