[#339] Support SigV4A #344
No reviewers
TrueCloudLab/storage-services-developers
Labels
No labels
P0
P1
P2
P3
good first issue
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#344
Loading…
Reference in a new issue
No description provided.
Delete branch "dkirillov/frostfs-s3-gw:feature/339-sigv4a_support"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
close #339
117725eb67
to978679f380
978679f380
to65b1a25f90
WIP: [#339] tmpto WIP: [#339] Support SigV4A65b1a25f90
to85a81d2f79
WIP: [#339] Support SigV4Ato [#339] Support SigV4A85a81d2f79
to58b193c8d9
@ -15,1 +19,3 @@
"github.com/aws/aws-sdk-go/aws/credentials"
"github.com/aws/aws-sdk-go-v2/aws"
credentialsv2 "github.com/aws/aws-sdk-go-v2/credentials"
"github.com/aws/smithy-go/logging"
What you think about modifying v4a code a bit to get rid of this logger?
I have no strong opinion on this matter.
I suggest you to try to remove all
smithy-go
imports from the code, if it is possible. To me it looks like completely redundant library for us.d7a1cfe6a3
tob8abf01bfa
@ -344,1 +401,4 @@
creds := aws.Credentials{
AccessKeyID: authHeader.AccessKeyID,
SecretAccessKey: box.Gate.SecretKey,
}
nitpick: consider rewriting in one line or use
credentials.NewStaticCredentialsProvider
a9633fee18
to9395b5f39d
Looks good, let's see how it going to work with S3 clients before gateway release.