As far as I can tell, the LagomConductRPlugin always starts Cassandra, with no easy way to disable it other than by completely redefining the installationData task.
It would be better if it respected the value of the lagomCassandraEnabled setting. Even better than that: introduce a conductrCassandraEnabled setting that defaults to lagomCassandraEnabled.value, so that they can be controlled independently if needed.
Workaround
The install task is just a convenience, and it isn't necessary to use it to run Lagom services in ConductR. The Lagom documentation on running services in ConductR explains lower-level commands that can be run individually to deploy each service. Alternatively, you could use install and then ; conduct stop cassandra ; conduct unload cassandra to disable it manually.
The Lagom development environment allows you to disable starting the Cassandra server for projects that don't use Cassandra (or use an externally-hosted one): https://www.lagomframework.com/documentation/1.3.x/scala/CassandraServer.html#Disable-it
As far as I can tell, the
LagomConductRPluginalways starts Cassandra, with no easy way to disable it other than by completely redefining theinstallationDatatask.It would be better if it respected the value of the
lagomCassandraEnabledsetting. Even better than that: introduce aconductrCassandraEnabledsetting that defaults tolagomCassandraEnabled.value, so that they can be controlled independently if needed.Workaround
The
installtask is just a convenience, and it isn't necessary to use it to run Lagom services in ConductR. The Lagom documentation on running services in ConductR explains lower-level commands that can be run individually to deploy each service. Alternatively, you could useinstalland then; conduct stop cassandra ; conduct unload cassandrato disable it manually.