Quarkus-Lambda: Is it really necessary to implement RequestStreamHandler instead of RequestHandler?

[hamburml]

Hello,

I am not 100% sure if this is the right spot for my question. Lets see :)
We want to use Dynatrace to monitor our aws lambdas.

Dynatrace can monitor AWS Lambdas https://docs.dynatrace.com/docs/setup-and-configuration/amazon-web-services/integrate-into-aws/aws-lambda-integration/aws-lambda-extension.

Dynatrace can monitor Quarkus https://docs.dynatrace.com/docs/setup-and-configuration/technology-support/application-software/java/quarkus.

Dynatrace mention that there are limitations, for example that the handler class must derive from RequestHandler. Quarkus has a own wrapper which implements RequestStreamHandler and the user developed handler is embedded within. https://github.com/quarkusio/quarkus/blob/main/extensions/amazon-lambda/runtime/src/main/java/io/quarkus/amazon/lambda/runtime/QuarkusStreamHandler.java

Is this really necessary? I forked Quarkus and simply rewrote the handler like that... (yes, the name of the class is obviously wrong :D)

public class QuarkusStreamHandler implements RequestHandler<InputStream, OutputStream> {

    private static final Logger log = Logger.getLogger(QuarkusStreamHandler.class);

    public QuarkusStreamHandler() {
        Quarkus.manualInitialize();
    }

    @Override
    public OutputStream handleRequest(InputStream inputStream, Context context) {
        OutputStream outputStream = new ByteArrayOutputStream();
        Quarkus.manualStart();
        log.info("RequestHandler instead of RequestStreamHandler");
        try {
            return AmazonLambdaRecorder.handle2(inputStream, outputStream, context);
        } catch (IOException e) {
            throw new RuntimeException(e);
        }
    }
}

The handld2 Method simply returns the outputStream. Sure, user defined RequestStreamHandler will not work anymore (i think?) but dynatrace should work out of the box if the docs are true...

I was able to build a lambda with 999-SNAPSHOT dependency and was able to call it.

Any thoughts on that?

Thanks!

[hamburml]

Looks like this isnt working that easy. I tried it in combination with quarkus-amazon-lambda-rest but the AWS API gateway always errors because "Malformed Lambda proxy response". But when I print outputStream it looks like a valid output.