[QUERY] ArmDeploymentResource.ValidateAsync doesn't return ArmDeploymentValidateResult but throws exception when "Preflight validation failed" about azure-sdk-for-net HOT 5 CLOSED

Thank you for your feedback. Tagging and routing to the team member best able to assist.

from azure-sdk-for-net.

Hi, @HarveyLink , fyi, the track1 SDK doesn't throw exceptions when "Preflight validation failed".

from azure-sdk-for-net.

hi @heng-liu

When working with Long-Running Operations (LROs) in the Azure SDK, the SDK typically throws an exception if a 400 response is returned by the service. This is intended to simplify error handling by treating non-successful HTTP responses as exceptions. However, this can be problematic if you need to handle 400 responses as non-exceptional cases, such as when you want to parse and process the validation result directly.

ARM Specification and Expected Behavior
According to Azure Resource Manager (ARM) specifications, LROs should not return a 400 status code as part of their standard operation flow. The expectation is that successful operations will return 200-series status codes, and failure scenarios will return appropriate status codes that are handled as exceptions. Due to this specification, the Azure SDK is designed to treat 400 responses as errors and throws exceptions accordingly.

Custom Handling Approach
To manage this, you can wrap the LRO call in a try-catch block and handle exceptions specifically for the 400 status code. This allows you to extract the necessary information from the response and handle it appropriately without treating it as an error.

Seeking Further Assistance
If the current SDK behavior does not fully meet your needs or requires more customization than you can implement, it is advisable to contact the Azure service team for further assistance. They can provide specific guidance or consider feature requests for future SDK updates. By reaching out to the service team, you can get specialized support and potentially influence future improvements in the SDK to better handle your scenarios.

from azure-sdk-for-net.

Hi @heng-liu. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text "/unresolve" to remove the "issue-addressed" label and continue the conversation.

from azure-sdk-for-net.

Hi @heng-liu, since you haven’t asked that we /unresolve the issue, we’ll close this out. If you believe further discussion is needed, please add a comment /unresolve to reopen the issue.

from azure-sdk-for-net.