-
Notifications
You must be signed in to change notification settings - Fork 78
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
Support waiting on multiple ports #129
Comments
Sure, it is not the same, but currently you can achieve the same passing each one of them as a single resource, or that doesn't work? |
@metcoder95 When I pass multiple resources, it waits for ALL of them to become available, not just one of them. |
That will be interesting, maybe worth it to explore an option like |
Or --first |
That would also works as a workaround for #133 if we could have this not just for ports, but full host/port combos! |
Currently
wait-on
only allows for you to wait until one or more known services have started.However the specific port that the service will be running on, isn't always known in advance, so I would like the ability to wait on a set of ports instead of a single port.
Example: Wait on port 7071 OR 7072.
Example: Wait on a port in the range 7071-7080
The text was updated successfully, but these errors were encountered: