-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
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
Support access to Connect services #106
Comments
Thanks for the report.
I doubt that's the case, so your contribution will be much welcome. I cannot easily find which version of Consul introduced this API, do you happen to know this? Looking forward to your PR. |
I do not know the version; that is a good question. But their introduction video was published in 2018 so I'm assuming it was around that time? |
It looks like it was introduced as a beta in v1.2.0. |
Just wanted to give a bit of a heads up that my company has bumped this down in priority for a short time. It's still on my plate but I won't be able to get to it immediately. I have something that I think is worth testing soon, but I'll have to set up a working test environment first. |
@LaoArchAngel How far did you get on this? Any chance you could share what you have, even though it is incomplete? |
One of the major features and offerings by Consul is the Connect service-mesh that provides secure communication between services. Both the HTTP API as well as the GO API provide a way to find these Connect services via the Catalog endpoint / object and would be very useful for dotnet apps trying to use these concepts as well.
https://www.consul.io/api/catalog#list-nodes-for-connect-capable-service
https://pkg.go.dev/github.com/hashicorp/consul/api#Catalog.Connect
I will be working on a PR for this if it's not already on someone's list as it's needed by my employer, but input would be very appreciated!
The text was updated successfully, but these errors were encountered: