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: Rename SSE related pairs to meet AOS-38 #38

Merged
merged 4 commits into from
Apr 22, 2021
Merged

storage: Rename SSE related pairs to meet AOS-38 #38

merged 4 commits into from
Apr 22, 2021

Conversation

xxchan
Copy link
Contributor

@xxchan xxchan commented Apr 22, 2021

@Xuanwo
Copy link
Contributor

Xuanwo commented Apr 22, 2021

The code looks like not formatted.

storage.go Outdated
input.XQSCopySourceEncryptionCustomerKey = &opt.SseCopySourceCustomerKey
input.XQSCopySourceEncryptionCustomerKeyMD5 = &opt.SseCopySourceCustomerKeyMd5
if opt.HasEncryptionCustomerAlgorithm {
key := opt.EncryptionCustomerKey
Copy link
Contributor

Choose a reason for hiding this comment

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

Maybe we can introduce a function like following:

func calculateEncryptionCustomerKey(algo string, key []byte) (algorithm, keyBase64, keyMd5Base64 string, err error)

service.toml Outdated
@@ -94,5 +86,5 @@ description = "set default pairs for storager actions"
[infos.object.meta.storage-class]
type = "string"

[infos.object.meta.sse_customer_algorithm]
[infos.object.meta.encryption_customer_algorithm]
type = "string"
Copy link
Contributor

Choose a reason for hiding this comment

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

Add an empty line here.

@Xuanwo Xuanwo changed the title rename encryption pairs, and calculate md5 for user storage: Rename SSE related pairs to meet AOS-38 Apr 22, 2021
@Xuanwo Xuanwo merged commit a47fc96 into master Apr 22, 2021
@Xuanwo Xuanwo deleted the sse branch April 22, 2021 07:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants