-
Notifications
You must be signed in to change notification settings - Fork 12
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
Ruby 3.2 Gem Path Error for AWS SDK #98
Labels
bug
Something isn't working
Comments
Quick and dirty fix that I did Starting at line 130
|
Just following up on this - would be nice to not have to monkey patch each of my projects |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AWS Lambda with Ruby 3.2 error - by setting the GEM_PATH environment variable, the native aws-sdk gems cannot load
Additional context
As outlined in AWS docs for including gems from layers (https://docs.aws.amazon.com/lambda/latest/dg/ruby-package.html#ruby-package-dependencies-layers), if the generated zip file structure changes from
ruby/3.2.0/*
toruby/gems/3.2.0/*
then there is no need to set the GEM_PATH environment variable which will eliminate the issue of the native aws-sdk gems not being found.Confirmed this works by compiling the
deploy_http_nokogiri
sample (https://navarasu.github.io/serverless-ruby-layer/#/use_docker), unzipping gemLayer.zip and adjusting the folder structure, zipping and manually uploading a custom layer to AWS.The text was updated successfully, but these errors were encountered: