quarkus-amazon-lambda and quarkus-smallrye-health in dev mod

[gquintana]

I created a Lambda application with Smallrye Health dependency.
I am using the HealthCheck framework but not the HTTP management endpoint.
The app refuses to start at least in dev mode and @QuarkusTest fails due to HTTP port usage:

# Dev Mode
2023-09-07 12:06:00,157 ERROR [io.qua.run.Application] (Quarkus Main Thread) Port 8080 seems to be in use by another process. Quarkus may already be running or the port is used by another application.
2023-09-07 12:06:00,163 WARN  [io.qua.run.Application] (Quarkus Main Thread) Use 'netstat -a -b -n -o' to identify the process occupying the port.

# Tests:
Caused by: io.quarkus.runtime.QuarkusBindException: Port(s) already bound: 8081: Address already in use: bind

I tried to set several settings:

quarkus.management.enabled=true
quarkus.smallrye-health.management.enabled=false
quarkus.smallrye-health.ui.enable=false

What is the solution to have smallrye-health dependency in Lambda application?
Is it possible to disable smallrye-health HTTP listener?

To reproduce create a project, add those 2 extensions:
https://code.quarkus.io/?a=test-lambda-health&e=amazon-lambda&e=smallrye-health
And run tests or dev mode

[quarkus-bot[bot]]

/cc @Ladicek (smallrye), @jmartisk (health,smallrye), @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda), @phillip-kruger (smallrye), @radcortez (smallrye), @xstefank (health)

[xstefank]

This is caused by amazon-lambda. Health is not required to reproduce this issue. I get:

Caused by: java.lang.RuntimeException: Unable to find handler class, make sure your deployment includes a single 
com.amazonaws.services.lambda.runtime.RequestHandler or, com.amazonaws.services.lambda.runtime.RequestStreamHandler implementation

[gquintana]

Your error is different. I have a Lambda handler in my code, and Quarkus code generator produces a GreetingLamda class implementing RequestHandler as well. The problem does not come from the lack of handler class.