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

[BUG] PageBlobUploadPagesFromURLHeaders missing field encryptionKeySha256 #5286

Closed
jaschrep-msft opened this issue Sep 6, 2019 · 2 comments · Fixed by #5440
Closed

[BUG] PageBlobUploadPagesFromURLHeaders missing field encryptionKeySha256 #5286

jaschrep-msft opened this issue Sep 6, 2019 · 2 comments · Fixed by #5440
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)

Comments

@jaschrep-msft
Copy link
Member

Auto-generated class azure.storage.blob.models.PageBlobUploadPagesFromURLHeaders has no field/getter encryptionKeySha256 for header x-ms-encryption-key-sha256, even though the service returns the header when using a customer provided key.

Access to this in the generated class is necessary, as azure.storage.blob.models.PageBlobItem, a handcrafted model class, exposes this field, and sets it on most of its constructors. But since this generated class doesn't expose this, the handcrafted class can't expose it in this particular method call.

@jaschrep-msft jaschrep-msft added bug This issue requires a change to an existing behavior in the product in order to be resolved. Storage Storage Service (Queues, Blobs, Files) Client This issue points to a problem in the data-plane of the library. labels Sep 6, 2019
@jaschrep-msft
Copy link
Member Author

In a similar vein, azure.storage.blob.models.AppendBlobAppendBlockFromUrlHeaders contains the encryptionKeySha256 but NOT the isRequestServerEncrypted field.

@kurtzeborn
Copy link
Member

@alzimmermsft, you were thinking this was a swagger issue.

@alzimmermsft alzimmermsft self-assigned this Sep 16, 2019
@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
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants