The provided description on this site about quarkus.openshift.arguments and quarkus.openshift.command are poor. I guess that quarkus.openshift.arguments talks about the program arguments. In case of a JVM mode would be the main argument that a developer could pass to their apps, and in the case of a Native app would be the program args.
Regarding quarkus.openshift.command I am not sure what does mean, I guess that must be the container command in case you want to overwrite the default one, so in the case of a JVM app could be something like: java -Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -jar /deployments/quarkus-run.jar
In both cases are missing a proper description on the following sites:
Describe the bug
The provided description on this site about
quarkus.openshift.arguments
andquarkus.openshift.command
are poor. I guess thatquarkus.openshift.arguments
talks about the program arguments. In case of a JVM mode would be the main argument that a developer could pass to their apps, and in the case of a Native app would be the program args.Regarding
quarkus.openshift.command
I am not sure what does mean, I guess that must be the container command in case you want to overwrite the default one, so in the case of a JVM app could be something like:java -Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -jar /deployments/quarkus-run.jar
In both cases are missing a proper description on the following sites: