If you pass a URL with an explicit /rest or The existing API should continue to work as expected, it's simply a backend detail.įrom /usr/bin/bugzilla there aren't any explicit command line options to force The Bugzilla API class also force_rest and force_xmlrpc init arguments toįorce use of a specific API for the passed URL. In practice this should mean previously used URLs will continue to use XMLRPC. Otherwise just attempt to initialize the XMLRPC backend.any JSON the API sends is what youll find in the. The contents of the DotDict reflects the exact output of the API, i.e. Everything is basically a DocDict (a dict() you can address like an object i.e. Try appending /rest and if the URL exists, use it You can and should get an API KEY from Bugzilla with a Bugzilla account to your instance, in the user preferences.Try appending /xmlrpc.cgi and if the URL exists, use it.Note though that is looking at disabling the XMLRPC API entirely, but they are usually ahead of the Bugzilla curve.īy default, python-bugzilla will use some URL parsing heuristics to try to guess if the On specifically the XMLRPC API is still recommended, because some custom features are not available over REST yet. In practice there isn't any released bugzilla version that has big differences between the two API versions. The main interesting bit it adds is support for Bugzilla's REST API.Īll previous versions of python-bugzilla and /usr/bin/bugzilla only used the XMLRPC API, but that is deprecated in Bugzilla 5.0+ and all new API development is taking place on the REST API.
0 kommentar(er)
