ethanrowe / auto-consul Goto Github PK

All existing commands should have meaningful exit codes:

• 0 for normal exit
• non-zero for non-standard exit

The heartbeat should probably exit with 255 if the agent isn't running (meaning it can't get information with the consul info call), and 0 otherwise.

The runner should probably exit with consul's exit code if consul exits with non-zero status. And otherwise exit with 0.

It should be possible to get an actual list of commands with reasonable help. The help shows parameters but not the commands, which ain't awesome.

Given a --heartbeat option, with a periodicity in seconds, the runner subcommand should issue heartbeats in parallel to the agent's running.

The agent should be monitored and the whole process should exit with the agent's exit code.

This will give us a single entry point for driving the whole utility as one unit.

Current auto-consul can automatically determine if it should be a server or an agent based upon passed in parameters. You should be able to tell auto-consul that it should explicitly be an agent or a server (even if this would violate the server numbers passed in via params)

Make sure signals are handled sanely in the runner now that we're going to make it manage multiple processes (the --heartbeat option).

If you're using port forwarding (for a container or VM), the IP consul agent advertises likely needs to be different from the binding IP. So, just as consul itself separates these, so must auto-consul.