[BUG] Create and Delete of ProtectedItem is asynchronous but not marked as long-running #31943
Assignees
Labels
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
Mgmt
This issue is related to a management-plane library.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Comments
thomas11
added
the
bug
microsoft-github-policy-service
bot
added
question
|
@hiaga Please help take a look, thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
API Spec link
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/recoveryservicesbackup/resource-manager/Microsoft.RecoveryServices/stable/2023-04-01/bms.json
API Spec version
2023-04-1
Describe the bug
The operations defined on /subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{vaultName}/backupFabrics/{fabricName}/protectionContainers/{containerName}/protectedItems/{protectedItemName} are long-running, i.e., the API returns a location header for clients to poll. However, they are not marked up with
"x-ms-long-running-operation": true, so clients generated from the spec will expect a synchronous response.Expected behavior
Clients generated from the spec know to poll for the results of these APIs.
Actual behavior
Clients generated from the spec expect the result in the response of the original request, which doesn't contain it.
Reproduction Steps
n/a
Environment
No response
The text was updated successfully, but these errors were encountered: