Will it be a problem to block main thread in quarkus command mode

[bboyz269]

A simple example that I want to persist multiple entities concurrently (sorry for kotlin)

@QuarkusMain
class CommandModeApp : QuarkusApplication {

    @ActivateRequestContext
    override fun run(vararg args: String?): Int {
        Panache.withTransaction {
            Uni.join().all(
                Entity(name = "1").persist().invoke { -> Log.info("Entity 1 persisted") },
                Entity(name = "2").persist().invoke { -> Log.info("Entity 2 persisted") },
            ).andFailFast()
        }.await().indefinitely()
        return 0
    }
}

2022-06-15 15:42:30,208 INFO  [org.hib.rea.pro.imp.ReactiveIntegrator] (JPA Startup Thread: default-reactive) HR000001: Hibernate Reactive
2022-06-15 15:42:30,365 INFO  [io.quarkus] (Quarkus Main Thread) command-mode 1.0.0-SNAPSHOT on JVM (powered by Quarkus 2.9.2.Final) started in 2.187s. 
2022-06-15 15:42:30,365 INFO  [io.quarkus] (Quarkus Main Thread) Profile dev activated. Live Coding activated.
2022-06-15 15:42:30,365 INFO  [io.quarkus] (Quarkus Main Thread) Installed features: [cdi, config-yaml, hibernate-orm, hibernate-reactive, hibernate-reactive-panache, kotlin, reactive-mysql-client, smallrye-context-propagation, vertx]
2022-06-15 15:42:30,741 INFO  [ac.me.CommandModeApp] (vert.x-eventloop-thread-0) Entity 1 persisted
2022-06-15 15:42:30,741 INFO  [ac.me.CommandModeApp] (vert.x-eventloop-thread-0) Entity 2 persisted
2022-06-15 15:42:31,143 INFO  [io.quarkus] (Quarkus Main Thread) subscription-status-update stopped in 0.022s

Is quarkus main thread blocked with .await().indefinitely() and does it defeat the purpose of reactive architecture?

[quarkus-bot[bot]]

/cc @evanchooly