Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Why is Consul using service tags instead of labels? #997
I was wondering, why Consul is using tags instead of labels. At the moment, if I wanted to add a value to a service which I need to parse in a Consul template, I had to use a prefix for the tag in order to identify the value within the template. E.g. if I was adding a hostname, I had to put "hostname_" as a tag, where "hostname" is the key / prefix and the value I needed to use in my template. I know that there is the key value store available, but I feel that this would not be the right place for storing this kind of information about a service, since it is service instance specific information and would get decoupled from the instance somehow. I guess, it should be bound to the service instance directly. To me, the key value store seems to be more the place for storing general configuration data.
Please let me know what you think about it and what would be your "best practice" in such a case.