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

Add Support For Azure Storage Options (Client Version) #681

Merged
merged 1 commit into from
Nov 22, 2020

Conversation

GGJason
Copy link
Contributor

@GGJason GGJason commented Nov 22, 2020

What this PR does / why we need it:
Azure Blob Health Checks Need Support For Custom Client Version

Which issue(s) this PR fixes:

No existing PR.
The original is that I use AzureStorage Health Check and I got an unhealty result with "Unhealty with 'null'" message.
I clone the source code and find the blob client return Header error that I solve in my application with set the client version to earlier version.
So I need to set the version of blob client to use the health check extension.
I fix it with adding an optional parameters in AddAzureBlobStorage Function and the related configurations.

Special notes for your reviewer:

Does this PR introduce a user-facing change?:
Yes.

Please make sure you've completed the relevant tasks for this PR, out of the following list:

  • Code compiles correctly
  • Created/updated tests
  • Unit tests passing
  • End-to-end tests passing
  • Extended the documentation
  • Provided sample for the feature

@unaizorrilla unaizorrilla merged commit 69589cd into Xabaril:master Nov 22, 2020
@unaizorrilla
Copy link
Collaborator

Hi @GGJason

Merged, on features/net50 I try to change the parameter order for BlobClientOptions. In this versions (3.3.1) this was a breaking change and I preserve your order!

A new release build is on appveyor, when finished a new package 3.3.1 will be published!

@GGJason
Copy link
Contributor Author

GGJason commented Nov 22, 2020

Thank you. It is very awesome to get such a fast response.

@sungam3r sungam3r mentioned this pull request Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants