clients/v1: Remove DeleteUser RPC from UsersService#98
Conversation
|
Thanks for cleaning things up, but you sure you actually read the DeepSearch thread you linked? It clearly says there is one downstream call site: https://sourcegraph.sourcegraph.app/search?q=context:global+repo:%5Egithub%5C.com/sourcegraph/sourcegraph%24+users().DeleteUser&patternType=literal We need to remove that call site first. |
unknwon
left a comment
There was a problem hiding this comment.
Request changes because we need to remove the call site that uses this method.
@unknwon it's technically not being used though, there aren't any handlers calling Do you still recommend deleting that first before merging this? |
Yes. BTW I think that's a requirement, not a recommendation, FWIW. |
fine! understood, will do 🫡 |
|
joe please stamp |
|
@unknwon callsites have been removed in #6809, hurry up and please stamp! |
I'm regret to inform you that your auto-stamp status has not been earned. |
How do I earn the auto-stamp status? can I be placed in a program? |
First of all, do all of the follow ups. |
part of CORE-1195: SAMS: remove DeleterUser endpoint from clientsv1, and user management RPC, and addressing @unknwon's comment
We initially implemented the
DeleteUserRPC to handle all CRUD user management actions in the Enterprise Portal, but since then we have decided not to implement any deletion functionality in Enterprise Portal. To clean up the UsersService API, removing this to avoid managing 2 separate DeleteUser implementations.Thanks to DeepSearch, this should be safe to remove as there are no downstream calls to the
DeleteUserRPCTest plan
CI