We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When Blob Public Access is disabled for Storage containers, delayed delivery is failing to create containers required for keeping lease locks.
Anyone using Azure Storage Queues transport with Blob Public Access disabled.
The transport passes an incorrect flag to the Storage API when a container needs to be conditionally created, PublicAccessType.BlobContainer or BlobContainerPublicAccessType.Container depending on the Storage SDK version.
PublicAccessType.BlobContainer
BlobContainerPublicAccessType.Container
Replacing the flag passed in with a stricter value, BlobContainerPublicAccessType.Off or PublicAccessType.None depending on the Storage SDK version.
BlobContainerPublicAccessType.Off
PublicAccessType.None
Originally raised on the public forum.
The text was updated successfully, but these errors were encountered:
Fixes #631
a4fde74
659c51c
9234116
Patches released: announcement.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Symptoms
When Blob Public Access is disabled for Storage containers, delayed delivery is failing to create containers required for keeping lease locks.
Who's affected
Anyone using Azure Storage Queues transport with Blob Public Access disabled.
Root cause
The transport passes an incorrect flag to the Storage API when a container needs to be conditionally created,
PublicAccessType.BlobContainer
orBlobContainerPublicAccessType.Container
depending on the Storage SDK version.Potential fix
Replacing the flag passed in with a stricter value,
BlobContainerPublicAccessType.Off
orPublicAccessType.None
depending on the Storage SDK version.Additional information
Originally raised on the public forum.
Affected versions
Backported to
The text was updated successfully, but these errors were encountered: