Feature Request: Add Devservices for Cassandra
Description
Environment
Pull Requests
Activity

Karan Dhingra April 25, 2023 at 12:05 PM
➤ Alexei Bratuhin commented:
Started working on it in https://github.com/coiouhkc/cassandra-quarkus/tree/feature/cassandra-quarkus-199-devservices

Karan Dhingra April 13, 2023 at 7:25 AM
➤ Alexandre Dutra commented:
> I recently gathered some experience writing a DevService for Mosquitto, is it OK if I try?
coiouhkc absolutely, be my guest
Also note that I'm not officially working on this project anymore, but I would gladly review your PR.
\cc absurdfarce

Karan Dhingra April 12, 2023 at 2:56 PM
➤ Alexei Bratuhin commented:
Hi adutra , I recently gathered some experience writing a DevService for Mosquitto, is it OK if I try?

Karan Dhingra May 13, 2022 at 8:04 AM
➤ Alexandre Dutra commented:
maxandersen unfortunately I'm very busy working for other projects right now and won't have time to look into this in a short-term time frame. If you have time to come up with a working prototype I'd be happy to review/test though.

Karan Dhingra May 12, 2022 at 2:55 PM
➤ Max Rydahl Andersen commented:
adutra anything we can do to help here ?
Details
Details
Assignee
Reporter

Since Quarkus 2.0 there are DevServices for some Plugins (DBs, Kafka, etc., e.g. https://quarkus.io/guides/datasource#dev-services-configuration-free-databases), see https://quarkus.io/guides/dev-services. They start a Container in docker, where you don't have to config something for it to run.
Also needed for this is a way to create the Schema on startup, possibilities:
something like the init_script.cql in the TestFramework
Implementing a Customizer, like https://quarkus.io/guides/rest-json#jackson
observer method, that gets the cassandra client injected
This would make usage of cassandra in Quarkus way easier, as one would not need to run multiple docker commands on every startup/change.
┆Issue is synchronized with a Github issue by Unito
┆Repository Name: cassandra-quarkus
┆Issue Number: 199