You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The consul namer currently allows specifying one tag to filter services, through the includeTag configuration key. That tag appears in the name like this:
One use-case is for resolving a service to a "preferred" service set, but also by service version. Two tag sets would be used; for example: primary and secondary, v1 & v2. That allows routing a v2 request preferably to a primary but only if it supports v2.
The text was updated successfully, but these errors were encountered:
The consul namer currently allows specifying one tag to filter services, through the
includeTag
configuration key. That tag appears in the name like this:The consul API supports searching with more than one tag.
That could be expressed by moving the tag to the tail of the path, interpreting as tags any residual fragments after the service name:
One use-case is for resolving a service to a "preferred" service set, but also by service version. Two tag sets would be used; for example:
primary
andsecondary
,v1
&v2
. That allows routing av2
request preferably to a primary but only if it supportsv2
.The text was updated successfully, but these errors were encountered: