Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LagomConductRPlugin should respect the lagomCassandraEnabled setting #277

Open
TimMoore opened this issue Jun 29, 2017 · 0 comments
Open

Comments

@TimMoore
Copy link

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 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant