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

Function Client AWS SDK V2 #2121

Closed
driverpt opened this issue Apr 30, 2024 · 4 comments · Fixed by #2130
Closed

Function Client AWS SDK V2 #2121

driverpt opened this issue Apr 30, 2024 · 4 comments · Fixed by #2130
Labels
type: enhancement New feature or request

Comments

@driverpt
Copy link
Contributor

Feature description

Using AWS SDK V2 for Underlying Function Client

@sdelamo
Copy link
Contributor

sdelamo commented May 3, 2024

can you elaborate what you ware requesting?

@driverpt
Copy link
Contributor Author

Apologies. So, currently function-client-aws is using aws-sdk-v1, which is bringing all of the aws-sdk-v1 dependencies along everytime I use it. If you plan on using aws-sdk-v2 exclusively, that may require extra dependencies and configurations to the projects.

TL;DR. We are requesting a function-client-aws-v2 which is dependent exclusively on aws-sdk-v2.

@sdelamo sdelamo added the type: enhancement New feature or request label Jul 2, 2024
@mbbush
Copy link

mbbush commented Jul 8, 2024

It would be great to see this released, as it would also resolve the authentication issues we're having with the current aws-sdk-v1 based function-client-aws, which only supports a short list of credential providers, which doesn't include what we need to run on EKS using IRSA.

I see the PR is approved; is there any estimate of when it might be merged/released?

@nathanpk-span
Copy link

Following up on @mbbush's comment -- do we have an ETA for this feature?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
No open projects
Status: No status
Development

Successfully merging a pull request may close this issue.

4 participants