Add set of command line arguments to easily read out from consul/etcd the registered services

[virtuald]

My use case is CoreOS systemd units, though this is a more general request. If I stick registrator on all of my cluster hosts, then when I bring things up and down they get into etcd without any mess. This is pretty sweet.

Now, I need to somehow pass the registered container addresses into my other containers when those containers start. I think that generally users would like to be able to do simple things like 'docker run $(registrator /some/service/key) my_container' and have that just work, instead of figuring out what weird etcdctl + sed madness I need to do to pass arguments to the container.

Arguably, one should probably integrate into etcd/consul directly. However, some services can't do that yet… I just realized that's what ambassadord is for. Hm. I feel that this type of functionality could be useful though.

[progrium]

You're on the right path but I can tell you now that what you're thinking
is outside the scope of registrator. If you figure out what you're looking
for I might be able to point you in the right direction with other tools.

But not as a registrator issue. :)

On Thursday, July 24, 2014, Dustin Spicuzza notifications@github.com
wrote:

My use case is CoreOS systemd units, though this is a more general
request. If I stick registrator on all of my cluster hosts, then when I
bring things up and down they get into etcd without any mess. This is
pretty sweet.

Now, I need to somehow pass the registered container addresses into my
other containers when those containers start. I think that generally users
would like to be able to do simple things like 'docker run $(registrator
/some/service/key) my_container' and have that just work, instead of
figuring out what weird etcdctl + sed madness I need to do to pass
arguments to the container.

Arguably, one should probably integrate into etcd/consul directly.
However, some services can't do that yet… I just realized that's what
ambassadord is for. Hm. I feel that this type of functionality could be
useful though.

—
Reply to this email directly or view it on GitHub
https://github.com/progrium/registrator/issues/2.

Jeff Lindsay
http://progrium.com

[virtuald]

I think you're right.