-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Allow StorageRequestValidationPipelinePolicy to be optional #53021
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
base: main
Are you sure you want to change the base?
Allow StorageRequestValidationPipelinePolicy to be optional #53021
Conversation
Thank you for your contribution @ThomasDebenham! We will review the pull request and get back to you soon. |
@microsoft-github-policy-service agree [company="LCP"] |
@microsoft-github-policy-service agree company="LCP" |
@microsoft-github-policy-service agree company="LCP" |
Fixes #52746 |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews |
This reverts commit c9621db.
@seanmcc-msft @amnguye @jaschrep-msft @jalauzon-msft @nickliu-msft Hi, how can I get this relatively simple PR to pass all of the checks. I have tried running the scrips the failed test suggest but it isn't working |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't believe this is something we can allow to be an optional feature. The echoing of the x-ms-client-request-id
is important in order to validate that the response received back is expected of the request that is sent.
Thank you for reviewing, if you look at the issue I posted here: #52746 The code seems to work fine if that exception is never thrown so I want it to be optional. Is there a potential issue somewhere else making them mismatch on the blob side? |
Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.