Azure / azure-sdk-for-go

This repository is for active development of the Azure SDK for Go. For consumers of the SDK we recommend visiting our public developer docs at:
https://docs.microsoft.com/azure/developer/go/
MIT License
1.65k stars 844 forks source link

[Recovery Services] Vague error messages when creating protected item #21808

Open Nutrymaco opened 1 year ago

Nutrymaco commented 1 year ago

Bug Report

{
  "error": {
    "code": "BMSUserErrorInvalidSourceResourceId",
    "message": "SourceResourceId must be a fully qualified ARM Id of source storage account. None."
  }
} 

The error message does not help to understand what is wrong with SourceResourceID.

lirenhe commented 1 year ago

We don't have the detail of the resouceId of each type would look like. Could you check the sample in https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/resourcemanager/recoveryservices/armrecoveryservicesbackup/protecteditems_client_example_test.go

github-actions[bot] commented 1 year ago

Hi @Nutrymaco. Thank you for opening this issue and giving us the opportunity to assist. To help our team better understand your issue and the details of your scenario please provide a response to the question asked above or the information requested above. This will help us more accurately address your issue.

github-actions[bot] commented 1 year ago

Hi @Nutrymaco, we're sending this friendly reminder because we haven't heard back from you in 7 days. We need more information about this issue to help address it. Please be sure to give us your input. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!

Nutrymaco commented 1 year ago

Hi, problem was that i build SourceResourceId with resource group of Recovery Service Vault and not resource group of File Share (they are not in the same group). But still error message was misleading, in my opinion it should say something like "Storage Account by provided SourceResourceId not found".

github-actions[bot] commented 3 days ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @adityabalaji-msft @pvrk.