-
Notifications
You must be signed in to change notification settings - Fork 27
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
Feature Request: Add Devservices for Cassandra #199
Comments
I would also like to see this. |
Thanks for reporting this, we are going to evaluate the suggestion. In the meanwhile, have you tried to use our test framework? |
I haven't but Dev Services is more than providing a running container at test time. It also kicks in when running Quarkus Dev Mode. |
I know :-) I was just suggesting a temporary workaround. |
@adutra anything we can do to help here ? |
@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. |
Hi @adutra , 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 |
Started working on it in https://github.com/coiouhkc/cassandra-quarkus/tree/feature/cassandra-quarkus-199-devservices, will raise a PR, once review-ready. |
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:
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 this Jira Task by Unito
The text was updated successfully, but these errors were encountered: