-
Notifications
You must be signed in to change notification settings - Fork 298
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
feat(compose): allow running specific services in compose #337
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
adding author annotations for easier understanding of my intent.
@tillahoffmann I've updated the tests to exercise the As a workaround I ended up exercising the |
Looks good; just a linting error to fix. |
fixed - can you rerun the tests for me and merge at will? I've started looking at the compose-v2 stuff but I'll move that onto the issue discussion (because v2 isn't a python package any more so rather would stick it to the issue instead of a PR) |
follow docstring recommendation from @tillahoffmann Co-authored-by: Till Hoffmann <[email protected]>
Thanks for the contribution! |
Hello there, I wonder if this feature is already included? or we still need to wait for a new version release? Thanks!! |
Not yet, but should be soon when #330 is merged. |
Changes
DockerCompose
class now has a new optional argument forservices
compose/__init__.py
for convenience (no properisort
right now, just this file)Issues
Should resolve #315 on a very basic level.
I'll be raising more PRs for QoL:
https://github.com/testcontainers/testcontainers-python/issues?q=is%3Aopen+is%3Aissue+compose