Why not use Consul KV to store tags and attributes?

[peebles]

I thing the idea of service attributes is good. Sometimes I want to associate more than an IP address and port with a service; I might want to store other attributes that are needed to gain access to that service. I still want the DNS functionality of Consul, so I cannot use the "consulkv" backend exclusively. Why not store the service attributes in a "parallel" location in the KV hierarchy? Or, is service attributes something already on the Consul/Etcd roadmap?

[dsouzajude]

I'd like that as well. It seems logical to have something like that.

[progrium]

Service attributes I believe were on the Consul roadmap. But not entirely sure. That also doesn't solve the problem for etcd. I think using KV for other attributes is a reasonable thing to do in a future release.

[ahus1]

Consul supports service tags. They have been around for some time (hashicorp/consul#26). Consul's documentation for services gives some information about this.

Attributes are disussed here hashicorp/consul#1107.