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

[Storage] Does BlobClient.Exists() function correctly for blobs encrypted with CPK? #18041

Closed
seanmcc-msft opened this issue Apr 14, 2021 · 3 comments · Fixed by #18106
Closed
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files)

Comments

@seanmcc-msft
Copy link
Member

Azure/azure-sdk-for-net#20361

@seanmcc-msft seanmcc-msft added Storage Storage Service (Queues, Blobs, Files) Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Apr 14, 2021
@tasherif-msft
Copy link
Contributor

Will implement this fix in Python

@seanmcc-msft
Copy link
Member Author

To clarify, the scenario is calling BlobBaseClient.Exists() with a BlobClient that does not have CPK, on a blob that does have CPK. We get 409 - blob encrypted with user-provided key from the service. Since the blob clearly exists, we should return true instead of throwing.

@tasherif-msft
Copy link
Contributor

Yep! makes sense

@tasherif-msft tasherif-msft self-assigned this Apr 15, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants