Problem: Several Commands for single instances (t5 some:thing) and for the client-management in the cloud are not sufficient to perform reliably client support.

 
a) OKAPI autodetection

• Adjust autodetection to find jetty11 container & select okapi-longhorn-148-snapshot-1 as default version
• Also add option in command, to setup a single plugin/service that is currently deactivated
• see: ServiceAutodiscoveryCommand, Plugins\Okapi\ConfigMaintenance

b) OKAPI purge

• Add parameter "server-name" allowing only the specified entry/servername to be removed

c) OKAPI command in the cloud ("tranlate5 okapi <option> ...")

• it should generally work similar to the client specific okapi command
• --add should add an entry OR update an existing entry with the same server-key. It MUST NOT set is as default-entry as currently implemented
• --purge should hve an optional argument to purge only the specified entry/server-name
• --update should (instead of updating an url as in the current state) set the default serverName by server-key
• The Commands must be always filtered to a certain version of t5 by default, so it is called like "translate5 okapi -v "7.18.2" -a http://t5-okapi-java11.web.inetsolutions.cloud:8080/okapi-longhorn-147/ . If no version is provided, a confirmation "are you sure" must be passed.
• only the --detail option does not need the version filter and instead add the version as column in the overview
• update command doc

d) "translate5 instance:foreach" command in the cloud

• It must be targeted by version via option and confirmation, just as the okapi-command

ONLY AFTER A TALK WITH THOMAS WHAT/IF MAKES SENSE:

e) "t5 database:prompt" command (is that even possible ?)

• We need to be able to open a DB-prompt in the cloud easily. Always doing it manually is waste of time & error-prone (typos instance-number <-> db-number)
• alias should be "t5 db"
• challenges: possible in our cloud architecture ? How to distinguish MySQL vs MariaDB ?