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
I think I caused a regression in #2467 -- from gitter:
git blame points to your commit 77d9b41 apparently before that change, servers did /v1/status/peers and clients /v1/agent/servers, but it got consolidated into /v1/agent/servers, which seems to be implemented in client only - so consul server health checks will fail on trunk
would it make sense to just switch the URI back to /v1/status/peers, as that seems to be a "generic" status check endpoint?
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
I think I caused a regression in #2467 -- from gitter:
The text was updated successfully, but these errors were encountered: