Is your feature request related to a problem? Please describe.
Right now we can't get the gossip info of a cluster by using the dotnet client.
Describe the solution you'd like
I think it would get nice to have a method in EventStore.Client.Operations, so we can get the gossip info of a given cluster. That would be handy for example when we force a resign of the leader, so we can check when the leader is a different node.
Describe alternatives you've considered
The only alternative I can think of is calling the HTTP endpoint, but we cannot use the cluster connection string. We will have to get that information from a particular node. If that node is down, try the next node, and so on, which is not ideal.
Additional context
In EventStore.Client.Operations there are methods to change the priority of resign a the leader, but I couldn't find a way to check the current status of the cluster.
Is your feature request related to a problem? Please describe. Right now we can't get the gossip info of a cluster by using the dotnet client.
Describe the solution you'd like I think it would get nice to have a method in EventStore.Client.Operations, so we can get the gossip info of a given cluster. That would be handy for example when we force a resign of the leader, so we can check when the leader is a different node.
Describe alternatives you've considered The only alternative I can think of is calling the HTTP endpoint, but we cannot use the cluster connection string. We will have to get that information from a particular node. If that node is down, try the next node, and so on, which is not ideal.
Additional context In EventStore.Client.Operations there are methods to change the priority of resign a the leader, but I couldn't find a way to check the current status of the cluster.
DEV-71