Danger: passwords on the command-line are a big no-no! That should probably be removed from examples, possibly adding a way to do it using environment or files.

***

It's amazing how much work people will go through to avoid using systemd.

I guess this is useful for portability to non-Linux though.

I guess the value of this is to encapsulate away various other command-line tools which could perform the same in a script. Lowers the barrier to entry. To my mind, though, this tries hard to tackle a solved problem.

On the other hand -- if it encourages dev teams to stop the silly habit of returning successful health checks from their microservices even before the back-end dependencies (DBs, other web services, etc) are ready, then it might have some value.

So the elevator pitch for this is "if wait-for [1] isn't sufficient and you want a go lang binary to evaluate the behavior or response of the request"?

https://github.com/vishnubob/wait-for-it

I however suspect that I wouldn't use it, if I was still working in devops. The niche where a simple wait for the port is insufficient is _extremely_ rare in practice... Because almost everything that needs such either already has the concept of a readiness check to make it available (k8s, LBs, etc) or will retry automatically given the port being open (DB connections etc)

this brings me back some inetd/xinetd memories.