-
Notifications
You must be signed in to change notification settings - Fork 420
fix(docs): make the Lambda Layer version consistent #3498
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
Conversation
3346cd5
to
7fa461c
Compare
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.
Hey @rubenfonseca!
1 - Should we balance the arm64 layer as well?
2 - Do you think is it possible to fix the description for new layers v54 in x86_64?
Thanks!
@leandrodamascena fixed everything, ready to look again |
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.
Just a last comment and it's good! Thanksss Ruben!!
Co-authored-by: Leandro Damascena <[email protected]> Signed-off-by: Ruben Fonseca <[email protected]>
Co-authored-by: Leandro Damascena <[email protected]> Signed-off-by: Ruben Fonseca <[email protected]>
|
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.
APPROVED!
Issue number: #3494
Summary
Changes
This PR fixes the inconsistent in the Lambda Layer version in our documentation. Now the layer version should be 54 in all supported regions.
We also updated the layer balancer code to support the most recent versions of Go.
User experience
After this PR, customers can again use the same Lambda Layer version number across regions.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.