I vote for this. That would make all the operations safer and easier. The only problem is that there are users who rely on legacy things. They might have done some context pipeline of work that takes those endpoints into consideration.
I have a plan to create a small script in Deno (JS) that gives the user a legacy endpoint tho.
Also, I gonna change this Add a Bulk Move Tablet and/or A deterministic scheme for Tablets (Also Geo-Sharding Support) to GraphQL. I think that would be way better to use the GraphQL layer for what I proposed there. I had mentioned the GraphQL Admin there, but with no examples.
@abhimanyusinghgaur BTW, I think this RFC should include Subscriptions. Cuz if we let it as just Queries, the user or the app (e.g. Ratel) will need to do a cron-job to pull that information. As naturally via HTTP it is updated on the fly (Ratel uses /health and other endpoints to gather information about the cluster). So subscriptions can do the trick.