Open paulsmithkc opened 1 year ago
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 —single
to just succeed when the first resource becomes avaialble
That will be interesting, maybe worth it to explore an option like
—single
to just succeed when the first resource becomes avaialble
Or --first
That would also works as a workaround for https://github.com/jeffbski/wait-on/issues/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