-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[Extension Proposal] Docker compose dev services #45338
Comments
/cc @aloubyansky (extension-proposal), @gastaldi (extension-proposal), @geoand (devservices), @gsmet (extension-proposal), @maxandersen (extension-proposal), @stuartwdouglas (devservices) |
That sounds really cool and would be a great candidate. Let's see what others think about it |
Definitely makes sense to have something in Quarkiverse |
Agreed I think @phillip-kruger also had some similar idea of allowing Generic Dev Services to be created but i like this idea because it allows you to use an existing Docker Compose Stack. |
@cescoffier mentioned that someone has done some work in this area, I can not remember who. |
It was actually @alesj |
no, at least I don't think so :) @alesj was doing other approach. someone had a pr/prototype allowing use of docker compose. was it @ozangunalp ? |
Maybe we can start from the first draft i did , that works for the basic use cases with compose files as dev services. Then we can see from there how we can integrate more complexe use cases and other ideas. |
@ozangunalp you had almost everything right? |
Description
Using dev services with quarkus is really great, but can be complicated when the service you want to use is not included in an already created extension.
There is no way to setup a dev service simply without creating an extension which can be complex at first, or using a
QuarkusTestResource
but the latter is limited to the tests.Docker compose is well known and often used in the same maner as the quarkus devservices, to startup containers for local development, local integration testing.
Using docker compose to bridge the complexity gap could be great as the services declared in docker compose files could be created and run as devservices by quarkus.
That would allow reuse across tests in the continuous testing mode, and starting and stopping them automatically in dev mode.
I created first implementation here https://github.com/Malandril/quarkus-docker-compose its still a work in progress.
Repository name
quarkus-docker-compose
Short description
Use docker compose to setup custom devservices
Repository Homepage URL
https://docs.quarkiverse.io/quarkus-docker-compose/dev/
Repository Topics
Team Members
Additional context
No response
The text was updated successfully, but these errors were encountered: