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

Allow DockerComposeModule to start only certain services #1497

Closed
HaMatthias opened this issue May 24, 2019 · 5 comments
Closed

Allow DockerComposeModule to start only certain services #1497

HaMatthias opened this issue May 24, 2019 · 5 comments

Comments

@HaMatthias
Copy link
Contributor

Hi everyone,

Actually I am using the DockerComposeContainer of Testcontainers for CDCTs of my services. For the provider verification it is necessary to start up the services, and that is the part, where Testcontainers helps me out.

Actually, my compose file comprises out of 22 services and 500 lines and I only want to start one of these services. So the enhancement of just starting up certain containers would be a really nice approach to me.

I really would like to see this feature and I will keep following the development of this framework. Thanks to the team of Testcontainers and keep going on like that you helped me a lot!

@HaMatthias
Copy link
Contributor Author

I already did some changes in my fork.
I can make a PR to this, would that be fine ?

@rnorth
Copy link
Member

rnorth commented Jun 6, 2019

Thank you - this sounds like an excellent proposal.

This actually makes a major improvement for one of my previous personal use cases for this, where I put services in separate docker compose files to enable this kind of split.

Your proposal is much better - thanks!

@dforegger
Copy link

We're trying to convert over to using the DockerComposeModule and since we're on docker-compose v3 we can't use the extends syntax. It'd be a pain to convert over to overrides, so we're really happy to see this and just in the nick of time (for us)!
Thank you HaMatthias! (and the testcontainers team, of course)

@rnorth
Copy link
Member

rnorth commented Jul 7, 2019

This was released in 1.11.4 🎉

@rnorth rnorth closed this as completed Jul 7, 2019
@willianantunes
Copy link

@rnorth I was in need of this feature. I tested with 1.13.0 (the latest one now) and sadly it does not work anymore. I had to use 1.11.4 version instead.

willianantunes added a commit to willianantunes/kotlin-playground that referenced this issue Mar 22, 2020
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

4 participants