For consistency with the CLI, and to avoid namespace clash issues with other sbt plugins, we need a single conduct command along with load, run etc as sub commands. One problem with the existing conductr configuration approach is that we cannot have a run command in place of start. run is already defined by sbt and has a different meaning. By moving to sub commands then we may have conduct run and avoid these style of issues.
Let's also have an ip and port sub command in place of controlServer (we should similarly have an ip sub command for the python CLI that sets up the env var accordingly).
For consistency with the CLI, and to avoid namespace clash issues with other sbt plugins, we need a single
conductcommand along withload,runetc as sub commands. One problem with the existingconductrconfiguration approach is that we cannot have aruncommand in place ofstart.runis already defined by sbt and has a different meaning. By moving to sub commands then we may haveconduct runand avoid these style of issues.Let's also have an
ipandportsub command in place ofcontrolServer(we should similarly have anipsub command for the python CLI that sets up the env var accordingly).