Skip to content

Maintenance: decrease aws-sdk usage #1404

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

Closed
1 of 2 tasks
dreamorosi opened this issue Apr 11, 2023 · 2 comments · Fixed by #1405
Closed
1 of 2 tasks

Maintenance: decrease aws-sdk usage #1404

dreamorosi opened this issue Apr 11, 2023 · 2 comments · Fixed by #1405
Assignees
Labels
automation This item relates to automation completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)

Comments

@dreamorosi
Copy link
Contributor

Summary

The repo uses aws-sdk (v2) to interact with AWS in several places related to integration tests. We should make an effort to phase out this usage in favor of the more modular AWS SDK v3.

Why is this needed?

Because the AWS SDK v2 is going to be put in maintenance mode in 2023, this way we'll be ahead of the curve when that happens.

Which area does this relate to?

Automation

Solution

Try to switch to AWS SDK v3 for JavaScript wherever possible.

Acknowledgment

Future readers

Please react with 👍 and your use case to help us understand customer demand.

@dreamorosi dreamorosi added automation This item relates to automation internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.) labels Apr 11, 2023
@dreamorosi dreamorosi self-assigned this Apr 11, 2023
@dreamorosi
Copy link
Contributor Author

As the linked PR states, the aws-sdk will still remain in the project in some capacity. The Tracer integration tests function code require the SDK to be present for the time being.

@dreamorosi dreamorosi added the completed This item is complete and has been merged/shipped label Apr 11, 2023
@github-actions
Copy link
Contributor

⚠️ COMMENT VISIBILITY WARNING ⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

@github-actions github-actions bot added the pending-release This item has been merged and will be released soon label Apr 11, 2023
@dreamorosi dreamorosi removed the pending-release This item has been merged and will be released soon label Apr 11, 2023
@dreamorosi dreamorosi moved this from Triage to Shipped in Powertools for AWS Lambda (TypeScript) Jan 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automation This item relates to automation completed This item is complete and has been merged/shipped internal PRs that introduce changes in governance, tech debt and chores (linting setup, baseline, etc.)
Projects
Development

Successfully merging a pull request may close this issue.

1 participant