Additional fix for #1160 when running Java lambdas locally #2378
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#1160 describes problems caused by AWS SDK classes from the localstack-utils-fat.jar overriding classes defined in the actual Lambda jar/zip itself. This causes numerous incompatibility problems.
I was able to isolate and repro this problem with a minimal example ( https://github.com/krrg/localstack-java-classpath-debug )
@whummer implemented a partial fix for this that moved the
localstack-utils-fat.jar
later on the classpath, but this fix only applied to lambdas being run using thedocker
executor.This PR takes a similar approach, but this time for lambdas being executed locally. Using the minimal example above, I verified that the classpath is now correctly ordered for local lambdas and that my example is able to be invoked without error.