Andy Damevin

This is already done but it will need to wait for 1.10: https://github.com/quarkusio/quarkus/pull/25397 Until then: https://github.com/quarkiverse/quarkus-quinoa/blob/main/integration-tests/pom.xml#L55 and https://github.com/quarkiverse/quarkus-quinoa/blob/main/integration-tests/src/test/java/io/quarkiverse/quinoa/it/QuinoaCodestartIT.java#L17

I am waiting for the CI to pass to give it a try

I've tried it with different cases and it seems to work fine (and as I expect it to work).

As this PR is side-effect friendly, I think it would be wise to have another review. @gastaldi maybe?

Ok, my concern using plain system properties is that we would have to find a way to filter them before passing them as data to codestarts if we don't want...

IMO we should reproduce the same syntax as for config on another named option (`data` or whatever), parse it using the same code as the data and passing the map...

@arpitbhardwaj would you give it a try?

@aloubyansky any thoughts?

There is not Quarkiverse extension with Codestart yet but it's possible. To add a codestart the first thing is to start from an empty code.quarkus.io project and add the code...

You need to make sure they are `unlisted: true` in the metadata. example: https://github.com/quarkusio/quarkus/blob/main/extensions/arc/runtime/src/main/resources/META-INF/quarkus-extension.yaml#L15