-
-
Notifications
You must be signed in to change notification settings - Fork 710
feat: Added support for event source mapping in alias submodule #320
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: Added support for event source mapping in alias submodule #320
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. Some simplification is required before merging.
Thanks for those suggestions, they have made it cleaner. |
Thank you for this addition! |
## [3.3.0](v3.2.1...v3.3.0) (2022-06-16) ### Features * Added support for event source mapping in alias submodule ([#320](#320)) ([af22d00](af22d00))
This PR is included in version 3.3.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
This change adds the ability to configure event source mapping on a Lambda Alias, instead of just the base Lambda. The code to configure the event source mapping was pulled from the main Lambda module and ported to the alias module.
Motivation and Context
We extensively target a Lambda alias for all our use cases in our environment, currently setting this purely via the module isn't possible.
Breaking Changes
No
How Has This Been Tested?
examples/*
to demonstrate and validate my change(s)examples/*
projectsRan terraform apply to
examples/alias
and then made my changes to the module and ran another apply. No changes were detected. Added new examples and ran another apply. Resources deployed successfully.pre-commit run -a
on my pull request