[META] Deprecate XMLRPC/JSONRPC API and support only REST going forward
Categories
(bugzilla.mozilla.org :: API, task)
Tracking
()
People
(Reporter: dkl, Unassigned)
References
(Depends on 1 open bug)
Details
(Keywords: bmo-on-deck)
We should deprecate and remove old API endpoints such as XMLRPC and JSONRPC. Also remove the BzAPI extension which was an older REST wrapper around XMLRPC.
Removing the old APIs may give performance gains but mainly reduce any future maintenance of that code.
JSONRPC is mostly unused as all use of it by the WebUI has been removed and was never really used by external clients much. XMLRPC sees little traffic except for a few hold outs which we can work with to convert them over to REST.
This tracking bug will be the parent of the other bugs which will be more small tasks such as code removal and communications.
Reporter | ||
Comment 1•5 years ago
|
||
dustin, I see that in the last 30 days, your account has been the majority of XMLRPC use of BMO. What is still using the XMLRPC API and is it something we can work together to convert over to REST?
Updated•5 years ago
|
Comment 2•5 years ago
|
||
I'm using https://github.com/ralphbean/bugwarrior. Is there a new API I should upgrade bugwarrior to use?
Please use the REST api documented at https://bmo.readthedocs.io/en/latest/api/index.html. I've filed ralphbean/bugwarrior/issues/697.
Comment 4•5 years ago
|
||
Thanks -- I posted some questions there.
Reporter | ||
Updated•2 years ago
|
Description
•