We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
var queryResult = await _consul.Health.Service(_config.KeyOfServiceInConsul, string.Empty, true); Tag is string.Empty
var queryResult = await _consul.Health.Service(_config.KeyOfServiceInConsul, string.Empty, true);
Old
"Routes":[ {"ServiceName":"ServiceName"} ]
New
{ "Routes":[ { "Service":{ "Name":"ServiceName", "Tag":[ "v1", "v2", "v3" ], "Datacenter":"dc1" } } ] }
The text was updated successfully, but these errors were encountered:
@842549829 What's your goal having Consul tags? Will you personally contribute to implement this feature?
Sorry, something went wrong.
@ggnaegi I'm not sure, but this issue about adding new Tag property to Service entry model, right? If Yes, we could add the property.
Tag
Dear @842549829, Update version to 23.3.0 With Consul Service Builder and Metadata features develop whatever you want. See more details in PR #2067
If you want official properties in route options then you have to contribute!
No branches or pull requests
Expected Behavior / New Feature
var queryResult = await _consul.Health.Service(_config.KeyOfServiceInConsul, string.Empty, true);
Tag is string.Empty
Actual Behavior / Motivation for New Feature
Old
New
The text was updated successfully, but these errors were encountered: