jcapriotti / apache-karaf-cookbook Goto Github PK

After a remove, it seems like something was still lingering...

karaf    25210  0.0  0.0 113252  1600 ?        S    Jan31   0:00 /bin/bash /opt/applications/karaf/bin/karaf server
karaf    25328  134 10.2 3173464 819220 ?      Sl   Jan31 13095:46 /usr/lib/jvm/java/bin/java -server -Xms128M -Xmx512M -XX:+UnlockDiagnosticVMOptions -XX:+UnsyncloadClass -Dcom.sun.management.jmxremote -Djava.endorsed.dirs=/usr

This effectively keeps a port open and prevents a reinstall from happening (because karaf can't be started and/or connected to)

Would you be able to add a '-s' to the bundle:install command so that the bundle starts up right away after it installs?

Automation using bin/client and default karaf user seems flaky. Use key-based auth. https://karaf.apache.org/manual/latest/security#_managing_authentication_by_key

All of the resources other than karaf are dependent on the install_path property match that set in karaf. Update the resources to share this value and master it in karaf.

Is it possible/better to create users through API calls, rather than editing users.properties?