-
Notifications
You must be signed in to change notification settings - Fork 47
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
Migrate aws-sdk-go v1 to v2 #1031
Comments
Happy to work on this task, just want to know if this is being tracked somewhere by the team. |
Hi @JoseAngel1196! While we're aware of this, no development has started yet. Please feel free to submit a PR for this. We'd love the contribution! 😄 |
oh nice -- yes I can take this. Will work on this! |
can you please assign the issue to me? |
Hey @sushantmimani @aka-bo I want to know what y'all think about this: should we consider creating a BREAKING CHANGE for this change? that means moving DynamoDB v1 client to v2 OR should i create a separate module for the v2 next to the v1? we might be able to reuse some of the code already in https://github.com/godaddy/asherah/blob/main/go/appencryption/pkg/persistence/dynamodb.go |
Hi @JoseAngel1196 , we're discussing this internally and will let you know soon. |
Hi @JoseAngel1196! We do not want to make this a breaking change. A separate package for v2 would be great. We were thinking of something along the lines of: .
├── cmd
│ └── example
├── integrationtest
│ ├── persistence
│ │ ├── persistencetest
│ └── traces
├── internal
├── pkg
│ ├── crypto
│ │ └── aead
│ ├── kms
│ ├── log
│ └── persistence
├── plugins
│ └── aws-v1
│ │ ├── kms
│ │ └── persistence
│ └── aws-v2
│ ├── kms
│ └── persistence
├── scripts We're currently working on the |
Amazing, I'll start working on this ASAP! |
See #1041 for the current state of the |
Is your feature request related to a problem? Please describe.
Are there any plans for when you are planning to migrate from aws-sdk-go v1 to v2? The AWS team has already set a deadline (reference) for when they plan to stop supporting the v1 AWS SDK for Go. They're encouraging everyone to migrate to v2.
The text was updated successfully, but these errors were encountered: