-
-
Notifications
You must be signed in to change notification settings - Fork 344
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
feat!: Update lambda module to 3.1.0 to support AWS provider version 4.8+ #166
feat!: Update lambda module to 3.1.0 to support AWS provider version 4.8+ #166
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks pretty good. Could you please apply these fixes and update the docs?
@antonbabenko fixes applied and docs updated |
Thanks @mattoddie ! |
## [5.0.0](v4.24.0...v5.0.0) (2022-03-31) ### ⚠ BREAKING CHANGES * - Update lambda module to 3.1.0 to support AWS provider version 4.8+ ### Features * Update lambda module to 3.1.0 to support AWS provider version 4.8+ ([#166](#166)) ([ea822a3](ea822a3))
This PR is included in version 5.0.0 🎉 |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Description
Due to the breaking changes in AWS provider 4.x, the lambda module used as part of this module has been updated to 3.x to support the new provider. To allow this module to be used with the new provider, we need to update the lambda module version.
Motivation and Context
This updates the dependent lambda module to version 3.x, allowing this module to be used with AWS provider 4.x.
Breaking Changes
This is a breaking change as it is no longer compatible with AWS provider 3.x.
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)pre-commit run -a
on my pull request