-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Multiple Address Support Request #23
Comments
Hi Ahmad, Thanks for your suggestion. It is an interesting feature. If we want to implement that with multiple arguments, Maybe it has a conflict with the #22 or other parts of Wait4X. Is it possible to explain your use case on the deployment process? Maybe I can suggest another solution. |
Hi Mohammad, As you know, we use By the way, I would be glad to contribute if you decide to have this feature. |
Hi Ahmad, Based on our conversation. You can try our new feature https://github.com/atkrad/wait4x#command-execution to have a single If the feature doesn't resolve your issue, I would gladly accept a pull request for that. |
Hi Mohammad, Thanks for your suggestion. It will reduce the number of |
Hi @anvari1313, Currently, Wait4X supports multiple inputs like this: wait4x tcp localhost:8081 localhost:8082 localhost:8083 -t300s It checks all of the inputs paralleled. I hope the feature can be helpful for you. |
What do you think about adding multiple addresses support? For example for HTTP it can be something like this:
If both
http://srv1:8080
andhttp://srv2:8080
return the expected result, wait4x exits successfully and otherwise it should be failed.Maybe we can use comma separated string that is mentioned above or split strings like this:
It can help us a lot to improve our deployment process.
The text was updated successfully, but these errors were encountered: