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

Support ruby 3.2 fix #51

Merged
merged 3 commits into from
Jul 30, 2023
Merged

Support ruby 3.2 fix #51

merged 3 commits into from
Jul 30, 2023

Conversation

lwoodson
Copy link

First two commits were reviewed in #50

Last commit is new and changes the following:

  • Moves the build-gems.sh script from the demo-service into the project root and ensures it is distributed with the npm package when released
  • Changes the docker command to execute the build to invoke the build-gems.sh script from bash in its new location.
  • Modifies the integration test to locally package and install the plugin into the demo-service at the start of each run

This upgrades the gem to support the new `ruby3.2` runtime
of which AWS says:

"Ruby 3.2 adds many features and performance improvements, including anonymous
arguments passing improvements, ‘endless’ methods, Regexp improvements, a new
Data class, support for pattern-matching in Time and MatchData, and support for
‘find pattern’ in pattern matching.

Existing Lambda customers using the Ruby 2.7 runtime should migrate to the Ruby
3.2 runtime as soon as possible. Even though community support for Ruby 2.7 has
ended, Lambda has extended support for the Ruby 2.7 runtime until December 7,
2023 to provide existing Ruby customers with time to transition to Ruby 3.2.
Functions using Ruby 2.7 continue to be eligible for technical support and
Lambda will continue to apply OS security updates to the runtime until this
date."

This also changes the docker image used to build the package dependencies from
the `lambci/lambda:*` images to the `amazon/aws-lambda-ruby:*` images provided
and maintained by AWS.  These images are the exact images used by lambda
functions using a ruby runtime.  They unfortunately don't have all the build
dependencies present in the lambci images.  Thus a wrapper script is provided
around the gem packaging in a docker container that ensures the necessary
packages are installed
- Rebase to get latest changes; regen yarn.lock file
- Remove commented out code in integration.sh (done in rebase)
- Remove documented ability to override the docker image
So that its installed with the plugin into node-modules and can
be invoked from a serverless project when bundling w/native
extensions.
@joshuaflanagan joshuaflanagan merged commit befdb0e into joshuaflanagan:master Jul 30, 2023
svestu added a commit to svestu/serverless-ruby-package that referenced this pull request Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants