-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Conversation
✅ Deploy Preview for label-studio-docs-new-theme ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
✅ Deploy Preview for heartex-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
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'} |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
/git merge develop
|
Codecov ReportPatch coverage has no change and project coverage change:
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 ☔ View full report in Codecov by Sentry. |
…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]>
PR fulfills these requirements
[fix|feat|ci|chore|doc]: TICKET-ID: Short description of change made
ex.fix: DEV-XXXX: Removed inconsistent code usage causing intermittent errors
Change has impacts in these area(s)
(check all that apply)
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)
What level of testing was included in the change?
(check all that apply)
Which logical domain(s) does this change affect?
(for bug fixes/features, be as precise as possible. ex. Authentication, Annotation History, Review Stream etc.)