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 was just wondering about the /v1/agent/check/deregister/<checkId> endpoint (https://consul.io/docs/agent/http/agent.html#agent_check_deregister). It seems that it works via a normal GET request, which seems pretty non-RESTful to me. The major problem is that it is easy to hit such endpoints without realising you're about to change the system.
Was there a reason not to favour an API where services were deregistered by a DELETE request to a URL such as /v1/agent/services/<checkid>?
I feel like I'm missing something as I don't see any other issues about this.
The text was updated successfully, but these errors were encountered:
Hi,
I was just wondering about the
/v1/agent/check/deregister/<checkId>
endpoint (https://consul.io/docs/agent/http/agent.html#agent_check_deregister). It seems that it works via a normal GET request, which seems pretty non-RESTful to me. The major problem is that it is easy to hit such endpoints without realising you're about to change the system.Was there a reason not to favour an API where services were deregistered by a DELETE request to a URL such as
/v1/agent/services/<checkid>
?I feel like I'm missing something as I don't see any other issues about this.
The text was updated successfully, but these errors were encountered: