Lazy loading of default SQSClient in order to make it work in quarkus /graalvm native about powertools-lambda-java HOT 5 CLOSED

Hi @argenstijn Thanks for opening the issue. Reason we initialise this static so that it can be done during function init phase of lambda execution model.

Is there a way to configure graalvm not to complain about it (without knowing much about graalvm ecosystem currently)? Something on the similar lines? https://stackoverflow.com/questions/60654455/how-to-fix-try-avoiding-to-initialize-the-class-that-caused-initialization-wit

from powertools-lambda-java.

Of course:

--initialize-at-run-time=software.amazon.lambda.powertools.sqs.SqsUtils

But the 'problem' is also that the default SQS is created even when you override it. In this situation it just unnecessary to load the default SQS.

from powertools-lambda-java.

Of course:

--initialize-at-run-time=software.amazon.lambda.powertools.sqs.SqsUtils

But the 'problem' is also that the default SQS is created even when you override it. In this situation it just unnecessary to load the default SQS.

Yeah I agree. I will configure it to lazy load, just wanted to see first that its not a blocker to make it run with graalv and there is a workaround the error.

from powertools-lambda-java.

from powertools-lambda-java.

Fixed in https://github.com/awslabs/aws-lambda-powertools-java/releases/tag/v1.7.2

from powertools-lambda-java.