Open EmersonPrado opened 10 months ago
Some basic facts require a big change:
So, I'm changing this issue to implement CLI API support, maybe as a common provider or shared library, which could serve wildfly_cli
and wildfly_resource
. And leaving the embedded server part for a future issue.
Proposal for code organization:
wildfly_cli::cli_api
command
parameterwildfly_resource::cli_api
state
parametercli_api
Custom resource wildfly_cli nicely executes JBossCLI/WildFly commands thru an HTTP connection to JBoss/WildFly server. But, in case we need to change any configuration before starting the server, we need to resort to the embedded server.
My proposal is to either write a new provider "embedded" to the existing type wildfly_cli. I managed something in a module used internally at work, but I think this would better suit this public module.