another (future?) option would be to make that script a plugin that the extension could register and then it would be workable on windows too.

Would it allow customizing the script though by the user?
An equivalent script for Windows could be added too, we should agree on the approach we want to take here.

You like the idea of depending on a codestart for basic functions to work? i.e. deploy, run, invoke, delete/undeploy?

I also don't like the idea of adding more to the pom. Extensions should be doing this automatically with config overrides being available. Can we have maven/gradle publish java compile version as an atttribute that extensions could find?

FYI: Azure Functions is in a good place. Going to be working on Lambda next to add quarkus:run, quarkus:deploy, and @QuarkusIntegrationTest features like I have for Azure Functions. Thinking of adding a quarkus:undeploy generic action too. The only thing missing really is quarkus:invoke, but only Lambda seems to have that action.

I haven't really put a lot of thought into this. Not sure what you have in mind as a roadmap. I just noticed most of the content is hardcoded and would be good if a user could adjust it w/o a rebuild re-generating it all. So just based on that I'd put it under resources.