Skip to content

feat: LSDV-3958: Server side encryption for Target Storage (AES256) #4180

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

Merged
merged 5 commits into from
May 14, 2023

Conversation

niklub
Copy link
Collaborator

@niklub niklub commented May 12, 2023

PR fulfills these requirements

  • Commit message(s) and PR title follows the format [fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made ex. fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
  • Tests for the changes have been added/updated (for bug fixes/features)
  • Docs have been added/updated (for bug fixes/features)
  • Best efforts were made to ensure docs/code are concise and coherent (checked for spelling/grammatical errors, commented out code, debug logs etc.)
  • Self-reviewed and ran all changes on a local instance (for bug fixes/features)

Change has impacts in these area(s)

(check all that apply)

  • Product design
  • Backend (Database)
  • Backend (API)
  • Frontend

Describe the reason for change

(link to issue, supportive screenshots etc.)

What does this fix?

(if this is a bug fix)

What is the new behavior?

(if this is a breaking or feature change)

What is the current behavior?

(if this is a breaking or feature change)

What libraries were added/updated?

(list all with version changes)

Does this change affect performance?

(if so describe the impacts positive or negative)

Does this change affect security?

(if so describe the impacts positive or negative)

What alternative approaches were there?

(briefly list any if applicable)

What feature flags were used to cover this change?

(briefly list any if applicable)

Does this PR introduce a breaking change?

(check only one)

  • Yes, and covered entirely by feature flag(s)
  • Yes, and covered partially by feature flag(s)
  • No
  • Not sure (briefly explain the situation below)

What level of testing was included in the change?

(check all that apply)

  • e2e
  • integration
  • unit

Which logical domain(s) does this change affect?

(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)

@netlify
Copy link

netlify bot commented May 12, 2023

Deploy Preview for label-studio-docs-new-theme ready!

Name Link
🔨 Latest commit 24c60a6
🔍 Latest deploy log https://app.netlify.com/sites/label-studio-docs-new-theme/deploys/6460b6baf720ed0007d476da
😎 Deploy Preview https://deploy-preview-4180--label-studio-docs-new-theme.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@netlify
Copy link

netlify bot commented May 12, 2023

Deploy Preview for heartex-docs ready!

Name Link
🔨 Latest commit 24c60a6
🔍 Latest deploy log https://app.netlify.com/sites/heartex-docs/deploys/6460b6b995115800088a5ee3
😎 Deploy Preview https://deploy-preview-4180--heartex-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@niklub niklub requested a review from wesleylima May 12, 2023 07:23
@github-actions github-actions bot added the feat label May 12, 2023
s3.Object(self.bucket, key).put(Body=json.dumps(ser_annotation))
additional_params = {}
if flag_set('fflag_feat_back_lsdv_3958_server_side_encryption_for_target_storage_short', user=annotation.completed_by):
additional_params = {'ServerSideEncryption': 'AES256'}
Copy link
Member

Choose a reason for hiding this comment

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

should it be enabled for all storages now?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I think so, since it's enabled by default in S3

@niklub
Copy link
Collaborator Author

niklub commented May 13, 2023

/git merge develop

Successfully pushed new changes:
Merge remote-tracking branch 'origin/develop' into fb-lsdv-3958 (fa3e17d)

Workflow run

@codecov
Copy link

codecov bot commented May 13, 2023

Codecov Report

Patch coverage has no change and project coverage change: +0.01 🎉

Comparison is base (9aeb3ad) 76.05% compared to head (24c60a6) 76.06%.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #4180      +/-   ##
===========================================
+ Coverage    76.05%   76.06%   +0.01%     
===========================================
  Files          156      156              
  Lines        11888    11893       +5     
===========================================
+ Hits          9041     9046       +5     
  Misses        2847     2847              

see 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@niklub niklub removed the request for review from wesleylima May 14, 2023 20:13
@makseq makseq merged commit 547330e into develop May 14, 2023
shayantabatabaee pushed a commit to shayantabatabaee/label-studio that referenced this pull request Sep 19, 2023
…umanSignal#4180)

* Add AES256 SSE encryption to S3

* Add feature flag

* Fix test fixture

* Address comments

---------

Co-authored-by: nik <[email protected]>
Co-authored-by: niklub <[email protected]>
@deppp deppp deleted the fb-lsdv-3958 branch November 14, 2023 18:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants