Skip to content
New issue

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

[BUG] Create and Delete of ProtectedItem is asynchronous but not marked as long-running #31943

Open
thomas11 opened this issue Dec 20, 2024 · 0 comments
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. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@thomas11
Copy link

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

@thomas11 thomas11 added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Dec 20, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

1 participant