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] Remove client-side encryption code from shared #24931

Merged
merged 11 commits into from
Jun 25, 2022

Conversation

jalauzon-msft
Copy link
Member

Previously the client-side encryption code lived in shared and therefore was present in fileshare and datalake even though those packages do not support encryption. This change moves the code out of _shared and into individual files inside just the Blob and Queue packages. This required a few changes as well as some mechanical changes.

  • Remove encryption.py from _shared in all packages
  • Create _encryption.py in Blob and Queue (duplicated code)
  • Adjust all the imports accordingly as well as clean up imports in a bunch of files
  • Move some upload logic out of the shared upload code and into the Blob specific upload code since the encryption code moved out of shared
  • Remove encryption options from base client and create StorageEncryptionMixin and add it to all Blob and Queue clients
  • Finally remove all encryption code from file-share and datalake

@ghost ghost added the Storage Storage Service (Queues, Blobs, Files) label Jun 21, 2022
@azure-sdk
Copy link
Collaborator

azure-sdk commented Jun 22, 2022

API change check

APIView has identified API level changes in this PR and created following API reviews.

azure-storage-blob
azure-storage-queue

Copy link
Member

@vincenttran-msft vincenttran-msft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks for this, as it looks like it was quite a hairy process 😨

@jalauzon-msft
Copy link
Member Author

/azp run python - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jalauzon-msft
Copy link
Member Author

/azp run python - storage - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@jalauzon-msft jalauzon-msft enabled auto-merge (squash) June 24, 2022 23:08
@jalauzon-msft jalauzon-msft merged commit 88055b3 into Azure:main Jun 25, 2022
iscai-msft added a commit to iscai-msft/azure-sdk-for-python that referenced this pull request Jun 27, 2022
…into merge_patch

* 'main' of https://github.com/Azure/azure-sdk-for-python: (155 commits)
  {machine learning} || Fix a bug in the code (Azure#24922)
  [CLU] support for AAD + docs (Azure#24960)
  Update dpg version (Azure#24986)
  [Botservice]fix model (Azure#24971)
  [perf] Add pipeline template and storage pipelines (Azure#24894)
  [Storage] Remove client-side encryption code from shared (Azure#24931)
  [EventHubs&ServiceBus] update docker images to internal (Azure#24966)
  Sync eng/common directory with azure-sdk-tools for PR 3481 (Azure#24964)
  [Dpg] update to use global autorest version (Azure#24970)
  [CLU] release updates + fix tests (Azure#24963)
  [Test Proxy] Add method to reset setting customizations (Azure#24952)
  [Storage] Add proxy-supporting test classes (Azure#24937)
  [Confidential Ledger] Enable live testing (Azure#24912)
  fix type of _SansIOHTTPPolicyRunner (Azure#24932)
  Adding SIP routing functionality to PhoneNumbers SDK (Azure#22805)
  [DPG] update quick-start-tool (Azure#24942)
  [formrecognizer] Enable copy model tests (Azure#24917)
  [CLU] remove maxpagesize (Azure#24949)
  Use westus3 for translation live tests (Azure#24947)
  [Storage] Make lease duration tests less flakey (Azure#24930)
  ...
@jalauzon-msft jalauzon-msft deleted the move-encryption-from-shared branch August 12, 2024 22:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants