setting Attrs with SERVICE_<metadata> about registrator HOT 11 CLOSED

Yeah, I don't think any of the backends actually support other attributes
yet. Soon Consul will.

On Tue, Oct 28, 2014 at 3:49 PM, joncolby [email protected] wrote:

I am using Docker with consul and tried this out the other day. I am
particularly interested in adding custom metadata to the Attrs data
structure, however I couldn't get this to work.

I tried setting a random metadata env variable such as
SERVICE_RELEASE=12345 and SERVICE_SERVERCLASS=SEARCH in the Dockerfile, and
the env variables are visible from inside the running container. However,
after querying the consul services I did not see and Attrs.

Overwriting Tags via the env variable SERVICE_TAGS did work however, so I
think I am doing it right.

any known issues with this? I don't know go so I didn't peek into the
source code.

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

Jeff Lindsay
http://progrium.com

from registrator.

Thanks for the quick answer. Registrator is a great idea and a cool project.

from registrator.

Thanks!

from registrator.

Guys, How can I get/set say "postgres" container "user" and "password" from consul using registrator?

from registrator.

Afaik Consul doesn't support attributes with services yet. They might eventually I think. As you can see from that linked issue it seems they will.

from registrator.

@progrium Yeah, but... how about using key/value for this?
i.e. "{SERVICE_NAME}:{ENV_VAR}" => "{ENV_VALUE}"
And we export all exposed container's envs

from registrator.

Maybe? That seems like a special case. It's more often you want to go the other way around from Consul KV to Docker environment. Seems like a third party module you could make after we improve module support.

from registrator.

Is it so special? Like the prev. example. Postgres exposes the username and password, and I need it everywhere I want to connect to the it. Otherwise registrator + consul still won't be useful for this use case. And yes, the other way around is to use consul template to get the user/pass

from registrator.

Yeah that sounds like the wrong way to go about that problem anyway.

On Tuesday, April 7, 2015, Gaston Morixe [email protected] wrote:

Is it so special? Like the prev. example. Postgres exposes the username
and password, and I need it everywhere I want to connect to the it.
Otherwise registrator + consul still won't help me in this case.

—
Reply to this email directly or view it on GitHub
#52 (comment)
.

Jeff Lindsay
http://progrium.com

from registrator.

How would it better? Thanks

from registrator.

Exercise for the reader :)

from registrator.