invoke-aws-lambda
invoke-aws-lambda copied to clipboard
AWS SDK for JavaScript (v2) will reach end-of-support on September 8, 2025
When using gagoar/[email protected] (currently the latest) there's a warning:
(node:1439) NOTE: The AWS SDK for JavaScript (v2) will enter maintenance mode
on September 8, 2024 and reach end-of-support on September 8, 2025.
Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check blog post at https://a.co/cUPnyil
(Use `node --trace-warnings ...` to show where the warning was created)
Is the migration going to be done? @gagoar
It will! I will have it done next week @varfrog!
Thanks Gagoar! Any update on when we might expect this? We are experiencing a bug relating to the underlying AWS SDK and hoping will be resolved with this upgrade 🙏 Suspect our issue is the same as this issue causing our production deploy to fail first time every time, then works fine second attempt. So weird.
Ouch, lost track of this issue. It should be fairly simple to update.
Okay, so for this change to be implemented, we are gonna face the following issues:
most users take @master as their base. instead of pinning it to a version
This could be solved, by keeping master as a branch and making main the V3 version. avoiding breaking changes for everyone unless desired.
Credentials provision changes for the new version.
The credentials universe comes with Providers now. Hence, I'm inclined to use
These will allow the same behavior as before (passing via env) and using it via parameters through the action. It will also add coverage for using roles via FromIni.
Hopefully, this makes sense to you. Please raise a concern if my vector of attack is confusing.
Apologies for the delay...
I like that versioning strategy.
If I'm totally honest the credentials/provider approach is detail I'm not quite across this minute, but so long as it works it doesn't matter much, that said passing through the action does sound ideal from a simplicity perspective.
@gagoar Hello! Is this still on your radar?
The versioning approach looks good, by the way. It might also be helpful to add a console warning on the master branch so that anyone who's out of the loop knows what they should update to.
This is already on @main branch if anyone here is wondering about it so you can switch @master to @main and it will work with the new version.
I've been slow to cut the new version but it should be fully functional on that branch
ping if you all wanna give it a try before I release. 🙏🏻 @Sheargrub @danwfeeney @varfrog