Authentication for Consumer deletion API call

Is there a plan in the roadmap for protecting the API call for consumer deletion?
If it is already present or being worked upon, please let me know.

https://github.com/linkedin/Burrow/blob/ece489ea9acb7dc226279f37a17f2dcaab187cb5/core/internal/httpserver/coordinator.go#L158

Start with core/internal/httpserver/coordinator.go at line 158 and inspect the consumer deletion API call. Determine the authentication requirement and confirm what endpoint behavior should change; done means the deletion call is protected and the expected behavior is documented or covered by tests.

Written by the indexing model from the issue text.