disable aws-lambda extension in custom profile with quarkus 3.0.0.CR1

[jimkont]

I volunteered to try out some features in quarkus 3.x, but I get some build errors when migrating my app to quarkus 3.0.0.CR1.

Our default profile uses the amazon lambda extensions, and this is the related configuration.

  lambda:
    handler: MyService
    mock-event-server:
      test-port: 9081
  package:
    type: fast-jar
  snapstart:
    generate-application-class-list: false

When I try to build with a custom profile using the following configuration,

  package:
    main-class: cli

The lambda extension is still enabled, and I get the following error

 [error]: Build step io.quarkus.amazon.lambda.deployment.ScriptGeneratorProcessor#buildScripts threw an exception: java.lang.IllegalStateException: java.nio.file.NoSuchFileException: build/quarkus-build/gen/bootstrap-example.sh
                at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:918)
                at io.quarkus.builder.BuildContext.run(BuildContext.java:282)
                at org.jboss.threads.ContextHandler$1.runWith(ContextHandler.java:18)
                at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2513)
                at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1538)
                at java.base/java.lang.Thread.run(Thread.java:833)
                at org.jboss.threads.JBossThread.run(JBossThread.java:501)
   Caused by: java.nio.file.NoSuchFileException: build/quarkus-build/gen/bootstrap-example.sh
                at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92)
                at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106)
                at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111)
                at java.base/sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:218)
                at java.base/java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:484)
                at java.base/java.nio.file.Files.newOutputStream(Files.java:228)
                at java.base/java.nio.file.Files.write(Files.java:3512)
                at io.quarkus.amazon.lambda.deployment.LambdaUtil.writeFile(LambdaUtil.java:50)
                at io.quarkus.amazon.lambda.deployment.LambdaUtil.writeExecutableFile(LambdaUtil.java:54)
                at io.quarkus.amazon.lambda.deployment.LambdaUtil.generateScripts(LambdaUtil.java:79)
                at io.quarkus.amazon.lambda.deployment.ScriptGeneratorProcessor.buildScripts(ScriptGeneratorProcessor.java:17)
                at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
                at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
                at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
                at java.base/java.lang.reflect.Method.invoke(Method.java:568)
                at io.quarkus.deployment.ExtensionLoader$3.execute(ExtensionLoader.java:909)
                ... 6 more

This was working fine in version 2.15.x. I guess that some configuration options changed in 3.x, and I need to update my custom profile to disable aws-lambda, but not sure where to look for the corresponding 3.x documentation. Any pointers?

[quarkus-bot[bot]]

/cc @matejvasek (amazon-lambda), @patriot1burke (amazon-lambda)

[jimkont]

no longer an issue in Quarkus 3.0.3